yes, to change the *effective* segment in BASIC/A is something like def seg = &hxxxx, where xxxx represents the start of the 64k segment. You'd still need to create a file, and right off the top of my head Debug offers as much utility for this as anything. Funky little problem is you can only save a file of 65535 bytes with debug, unless someone can tell me how you can save an entire 64k chunk of data... --- "Richard A. Cini" <rcini at optonline.net> wrote: ______________________________________________________________________________ http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs… ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow

--- Chuck Guzis <cclist at sydex.com> wrote: generally speaking, if a cpu board has 2 roms, designated high and low, would they also alternate addresses in the same way. And frankly, why would it matter, if you were just looking to save the contents? You could always stitch the code together afterwards. Didn't the IBM PS/2 models 25 and 30 do this with their ram - one bank had all the even numbered addresses, the other the odd? ____________________________________________________________________________________ Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/

On Wed, 29 Aug 2007, der Mouse wrote: deliberately? An accessory for the Epson RC20 Wrist computer was a "ROM Roader" (SIC) that was a little box with a ZIF socket and a serial cord (mini-phone)

Okay, I'll see if I can't put together a schematic. I did that, once. I have a TVI955 (what would now be called a dumb terminal, but in its time was called a smart terminal). It includes three ROMs. One is the terminal firmware, one is a character generator, and one is a user-supplied firmware (there's an escape sequence in the standard firmware that jumps to the user-supplied firmeware). I once put together a simple game that ran entirely in the terminal, in the user-supplied-firmware ROM.... I pulled the character-generator ROM and replaced it with flying wires to a breadboard on which I had a similar amount of RAM, plus logic to allow a host to write to it via a serial line. This gave me downloadable characters. It wasn't a very good setup; something about it (the flying wires, at a guess) produced lots of read errors, appearing as snow on the screen. And the way the host wrote to it was cycle-stealing; while the host was writing, the read circuits got garbage - 0xff, or the data being written, probably - which produced more artifacts on the screen. Definitely not suitable for firmware, for which read errors would be fatal, but tolerable for hacking around with character bitmaps. Unfortunately that breadboard circuit has been torn down long since. But I still have the ROM-reader circuit; I'll put together a schematic and parts list for that and drop a note here when it's done. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse at rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B