I was thinking like "ok, there are two extra ROM sockets, so they should be ROM A and B, no idea what the ROM9 is". Olaf: spot on, both about the memory location and that I was using 8032: the Visicalc ROM was supposed to be at ROM9, and now it's working! I can now run my original VisiCalc disk's image with the dump of the original protection-ROM inside xpet, great! Thanks. -- Ville > Rhialto <rhialto@falu.nl> kirjoitti 19.10.2014 kello 20.18: > > On Sun 19 Oct 2014 at 16:41:53 +0300, Ville Laustela wrote: >> I couldn't test these in emulator as I have no idea how the KRAM is >> supposed to work (even on the real hardware). I have a d80 of the >> chip-protected Visicalc disk, but I couldn't figure out how to attach >> the BIN file to VICE emulator (tried as ROM A/B, but then the emulator >> wouldn't reset: only black screen). > > It could be a ROM at $9000, in wich case the command line option is > "-rom9 file.bin". It shouldn't affect resetting though, since the PET > reset routine does not look at those addresses at all. Except on Basic 4 > machines such as the 8032 where the $B000 space is already taken by the > larger Basic ROMs. So it could only be -rom9 or -romA in your case. > > -Olaf. > -- > ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for > \X/ rhialto/at/xs4all.nl -- 'this bath is too hot.' Message was sent through the cbm-hackers mailing listReceived on 2014-10-19 19:00:02
Archive generated by hypermail 2.2.0.