• Please review our updated Terms and Rules here

CBM PET 3032 STRANGE BOOT

Didn't we get up to 30 something at one point?

I would just leave it run until you decide to go to bed... Then post how many successful passes we have achieved and switch it off for the night.

I would then remove Nivag's card - and put the CPU back in the mainboard, and give it another run tomorrow.

The more hours we get of successful passes, the more happy we should be...

Dave
 
Didn't we get up to 30 something at one point?

I would just leave it run until you decide to go to bed... Then post how many successful passes we have achieved and switch it off for the night.

I would then remove Nivag's card - and put the CPU back in the mainboard, and give it another run tomorrow.

The more hours we get of successful passes, the more happy we should be...

Dave
Ok thanks so much sir!
 
Hi, i turned off the Pet without crashes! 46 passes dram! time to? Goodnight!
 
So that probably indicates that the problem was related to either your 2K PETTESTER EPROM or the UD8 socket. But you changed the UD8 socket for a good one didn't you?

Dave
 
So that probably indicates that the problem was related to either your 2K PETTESTER EPROM or the UD8 socket. But you changed the UD8 socket for a good one didn't you?

Dave
Yes Dave, i changed ud8 socket for two times 😭
 
So, with Nivag's board you actually have everything on board you need:

1. You can switch the NOP link ON to enable the NOP generator.

2. You can use the PET's dynamic memory or you can use the static memory on Nivag's board to replace the PETs.

3. You can use the PET ROMs, or selectively use the ROMs configured into Nivag's board.

4. You can select different ROMs if you have them mapped onto Nivag's board. These include my PETTESTER or different versions of PET BASIC.

So, once you have put Nivag's board into a PET, you should never have to exchange ROMs again (unless they prove to be faulty of course).

Dave
 
So, with Nivag's board you actually have everything on board you need:

1. You can switch the NOP link ON to enable the NOP generator.

2. You can use the PET's dynamic memory or you can use the static memory on Nivag's board to replace the PETs.

3. You can use the PET ROMs, or selectively use the ROMs configured into Nivag's board.

4. You can select different ROMs if you have them mapped onto Nivag's board. These include my PETTESTER or different versions of PET BASIC.

So, once you have put Nivag's board into a PET, you should never have to exchange ROMs again (unless they prove to be faulty of course).

Dave
Great!!! So what can i do again for this pet? Can i try remove nivag a board and run pet with original roms?
 
The PETTESTER F800 variant... can checksum the editor ROM, if I remember correctly.... I would like to see it producing the correct numbers for the real editor ROM. (And in particular those numbers to not be changing)

Alternatively use the VOSSI tester which does a simple sum on the editor ROM socket.
 
Great!!! So what can i do again for this pet? Can i try remove nivag a board and run pet with original roms?
You can put all the ROMs back in now, the CPU back in and try to run the PET.

It is a good idea to check the ROM checksums in their sockets because that also allows a check on all the connections leading to the ROM.

But, there are other ways to check your ROM IC's. You can dump them into you programmer and do a file comparison with the ROM files on Zimmers. Most ROM burner software has this function, or you can use a Hex Editor program which also has the comparison function. It is possible to have normal checksums and the bytes be corrupted, but it might not be that common. But I like the file comparison method myself because you can be 100% sure, that the ROM file is normal and every byte is correct.

For my dynamic PET, which came with some faulty ROM's and an incorrect ROM, I created a duplicate set of ROM's for the whole machine. Each one tested and verified in the programmer. To find the defective original ROMs in the machine initially, I simply fitted the whole new set to the computer in one go, then one by one started substituting the old ones back in, this quickly found the defective original ROMs in less than 15 minutes. Then I also confirmed they were defective by examining their dumps in the programmer. The defective ones were badly corrupted. Now I just keep this set of duplicate known good ROMs in my "PET repair kit" and regard them as a "service tool".
 
Yes,

With the Nivag F800 PETTESTER 4K ROM in socket UD9 and the other BASIC ROMs (including the EDIT ROM in UD8) inserted in their correct sockets.

Dave
 
FYI.... FDBF is the Checksum-16 of edit-2-n.901447-24.bin

and

DD67 is the Checksum-16 of 2K worth of 00s followed by PETTESTE2KF04.bin :)

What would actually being tested would depend on if the ROMulan RAMulator were fitted and if it were which jumpers were in which positions... Assuming that it is currently NOT in the machine then things are looking encouraging.
 
Last edited:
FYI.... FDBF is the Checksum-16 of edit-2-n.901447-24.bin

and

DD67 is the Checksum-16 of 2K worth of 00s followed by PETTESTE2KF04.bin :)

What would actually being tested would depend on if the ROMulan RAMulator were fitted and if it were which jumpers were in which positions... Assuming that it is currently NOT in the machine then things are looking encouraging.
Hi Nivag, yes in this moment i haven't ROMulator on board....i have only cpu on board!
 
Back
Top