• Please review our updated Terms and Rules here

CBM PET 3032 STRANGE BOOT

Is this the same PET as was described back in the thread "PET 2001N horizontal line" that we installed the two wires between UD6/19 and UD7/19 and between UD6/22 and UD7/22?

Dave
Not...i don't believe....
 
i am desperate...i don't remember unfortunately :(
Well, are there some wires on the back of the board between UD6 and UD7? Also, have the UD6 and UD7 sockets been replaced?

You also don't need to remember if you keep a logbook of repairs, and include the board serial number...

Dave
 
>>> so..i leave nivag s board with these setting and i replace only ud8?

Yes.

All of Nivag's ROM links should be set to OFF now. Is this correct?

Dave
 
I AM REALLY DESPERATE NOW!
I turned on with original ud8 eprom and i have normal basic screen.....but why??? Nivag's board is in socket now!
 
I AM REALLY DESPERATE NOW!
I turned on with original ud8 eprom and i have normal basic screen.....but why??? Nivag's board is in socket now!

Why are you desparate (and in capitals)?

With Nivag's board configured with all of the ROM links to OFF it is using all the ROMs in the PET. You haven't got the PETTESTER mapped in on Nivag's board - if that is what you were thinking?

Are you sure you know what Nivag's board is actually doing for you?

Dave
 
With Nivag's board configured with all of the ROM links to OFF it is using all the ROMs in the PET. You haven't git the PETTESTER mapped in on Nivag's board - if that is what you were thinking?
oh yes...it's true!! With Nivag's board set to off, now i have only pet roms! So this mean that Pet is now working??
 
oh yes...it's true!! With Nivag's board set to off, now i have only pet roms! So this mean that Pet is now working??
Correct!

Now, what you have to work out is:

1. Does the PET now work by accident, in which case it will go faulty again... or

2. Your PETTESTER EPROM you were using is faulty.

Dave
 
Ok,

Can you change Nivag's board and set the ROM E link ON (to enable Nivag's PETTESTER code).

Then swap the ROM in socket UD7 for your PETTESTER EPROM.

Give it a run...

What we are going to do is to checksum the PETTESTER ROM in socket 'd'.

The PETTESTER code will think that there is a 4K ROM in UD7, so it will attempt to check it twice. I will have to compensate for that if I can.

Can you ensure the 'd' checksum that is displayed is stable. If it isn't, we can't use this test.

Dave
 
Back
Top