Ok, I've managed to image my rom using both INTELO and my TL866. Rather amusing bit about the "Chip ID". I hadn't thought about that, back in the day when I actually used to play with EEPROMs there was no such thing as "Chip ID". Thank you all for that.
Any tips to loading the rom in the emulator? When I do my call 63012, it simply gets stuck in a loop of some sort. I watched the loop counters for a while in decrement a few locations in memory for long enough to realize it wasn't ever going to exit the loop. Is there a better emulator than VirtualT? Any hints on building boards to drop new option roms into the 102? Thanks to all! On Thu, Mar 16, 2017 at 10:57 AM, Bryan Ard <[email protected]> wrote: > That's gold! I'm going to try INTELO tonight when I get home! Thanks! > > On Thu, Mar 16, 2017 at 6:58 AM, Mike Stein <[email protected]> wrote: > >> Just to clarify: >> >> R2D (ROM to Disk) copies the option ROM contents to a TPDD disk drive or >> an emulator such as the dlplus that Brian used. When you replace the option >> ROM with RAM this becomes sort of a 'poor man's REX' where you originally >> save 'real' ROMs (or modified ones) to the disk or PC (using R2D) and >> subsequently load whichever one you want to use back to the laptop from the >> TPDD or PC with D2X. >> >> ROMCOM (ROM to COM) sends the option ROM image out the serial port in >> binary format to be captured by a terminal program or similar. >> >> INTELO (Intel Out) also sends the option ROM image out the serial port, >> but as an Intel format ASCII file, as used by most EPROM programmers. >> >> m >> >> >> ----- Original Message ----- >> *From:* Brian White <[email protected]> >> *To:* Model 100 Discussion <[email protected]> >> *Sent:* Thursday, March 16, 2017 2:21 AM >> *Subject:* Re: [M100] Help Imaging a ROM >> >> >> I just tried r2d from that same EME support page that Mike referenced, >> and confirm it works. Nice. >> >> ftp://ftp.whtech.com/club100/eme/r2d100.100 >> >> >> >
