AF2 currently uses OS-9/68K v2.4 operating system this is a very old and.Thank you for your help. Display what the frame grabber and software are doing with the image of the. •The 68k Mac emulators (Basilisk II, Fusion PC and SoftMac) can use either 512 KB or 1 MB ROM images. Posted: (1 day ago) Capturing a Mac ROM Image E-Maculation wiki On roundup of the best images on Images.Posted: (1 week ago) Macintosh Os Emulator Images - imageslink.org Search Best Images Images.It works, but seems a dangerous method because writing boot with PUTBOOT would potentially corrupt the previous drives.My truly burning question was how to transfer files to/from PC (Windows Vista) to CP/M. My method was adding successive drives each with track offset greater than the total tracks of the previous drives. OS-9/68000 V2.4 Microware Systems P32 90/11/24 14:51:12.I'm also interested in how you created 4 (or more) drives on a CF. Covers version 3.x of the OS-9 Operating System but essentially the same as for v2.4 and v3.0.prohibits any reproduction of the software on tape, disk or any other medium except for backup. A guide to porting the RadiSys (nee Microware) OS-9/68k Operating System to new hardware.It works, but I can think of many ways it'd blew up. Then move the CF to the CP/M machine, located the beginning of the image and copy it starting from sector 0 of the CF. The way I go from PC to CP/M was to create a CP/M image with cpmtools and write the resulting image to a newly (FAT16) formated CF.Then you can copy (with PIP?_) the A: filesystem to B:, C:, or D. Full track, and other caching methods would take a lot more work.> I'm also interested in how you created 4 (or more) drives on a CF.What I did was to create a filesystem for the first drive, mount the CF, and initialize (with INIT) the other 3 drives. The simple approach is what I used (I think).
Os9 68K Emulator - -Os Dsk Image Software Are DoingMost terminal emulators have a capture function. Works most of the time.> I have absolutely no idea how to transfer CP/M back to FAT16-I'm just not smart enough today to write a FAT16 driver in CP/M.No need. I convert source files to S-records and move them over that way. Dd will also work, but is more dangerous.> My truly burning question was how to transfer files to/from PC (Windows Vista) to CP/M.I wrote a little utility that reads S-record files, and saves them to "disk" (the CF). I'm a Linux guy, so this is pretty easy to do. You can also use cpmtools to build B:, C:, or D: and then write a little C code to move over the first "disk" and copy to another. Would love to get a CPU like that going. I wrote a little application that I call "eatdmp" that converts dump format back to binary, and there are a number of applications you can find on-line to work with S-records (the output from "SENDC68").I'm really interested in your work with 68020, 68030, etc. 68k CP/M also has a DUMP application, and one called "SENDC68" (I think I remembered that name correctly?_) you can use to display binary, and again capture it with your emulator. Canon xf utility download for macI designed them to make sure that parts & tools I have on hand are working. Heavy sigh!Thank you for your interests in the 68020 & 68030. Somehow I need to find space on my cluttered desk to accommodate another box and monitor & learn another operating system. That may well be the solution in the near term.From what I have read in the past year on the subject of retrocomputing, A Linux machine appeared to be a critical tool. I put my BIOS code as it stands today in here for your reference.Thanks for the suggestions of using S Record file transfer & terminal screen capture to move data to/from CP/M and PC. But, there are strong similarities too, such as the 100h reserved area that is the "base page". To be at the highest memory addresses. I find that 68k CP/M is quite different than the Z80 CP/M that I'm most familiar with. I'll take a detailed look. I want to explore the world of DRAM, IDE, VGA, Ethernet and Operating Systems with cheap 68000 designs and then migrate the hardware designs into 020, 030 and even 040.Thanks for your BIOS code. Just pump out the data in a tight loop, at ~115k baud.I also do not initialize the DUART in the BIOS since it is already initialized in my monitor.Both our drives are the same size, 8 megabyte. I've found that the 68k doesn't even need to look at the status bits when it sends. These things can transmit across USB at speeds that are truly amazing. I start it up from a monitor that does that! Also note that I only use lba0 and lba1, so lba2 and the bits of lba3 that are available can be used to address other "drives" on the CF (with much more programming).If screen capture is too slow for you, take a look at the parallel to USB adapters that can be found on eBay (such as velopment-Module-Kit-USB-TO-parallel-FIFO/251042147761?ssPag eName=STRK%3AMEBIDX%3AIT&_trksid=p2060353.m1438.l2649)_. I used the same procedure as CPM15000.SR and make sure the BIOS is linked correctly. It is based on FTDI's FT232H.It is another reference design for adding high speed transfer capability.On a different topic, are you the same Roger on comp.os.cpm a few months ago who was having trouble running CPM400.SR? I want you to know that I have problem with CPM400.SR as well. In the back of my mind I expect to be burnt by this little trick sooner or later.Retrobrew forum member 'will' has designed a USB FIFO for file transfer. This is because when I processed the CP/M image created by cpmtools, I did the byte swap and then copy the byte-swapped image back into a CF starting from sector 0, thus creating a CP/M disk partition with bytes already swapped. You may noticed that I don't do byte swap when I read the 16-bit data. It won't be quite this simple when block/deblock algorithm is implemented.I gather your CF is bus connected with 16-bit data bus, just like mine. ![]() It compiles an application OK, but when I try to run the result I get exceptions. I'm running with DTACK* grounded at 12 MHz, but I cannot get the Digital Research BASIC compiler to work properly. I'm experimenting with using delay lines now to get the timing right, and it seems to work most of the time. It seems to be speed limited too, maybe 6 or 7 MHz, on top of that. USB transfer can be very fast!!>. There are a number of parallel to USB devices out there (one very expensive one is made by FTDI). Well, very similar to what I was suggesting. It is based on FTDI's FT232H.Yep, that's the one. Haven't figured out why.So, what is the secret of your CF interface? Is the difference programmable logic?> Retrobrew forum member 'will' has designed a USB FIFO for file transfer. Maybe some day I'll work on relocating an image a little lower in memory, but as you say with all that memory, is it worth worrying about? I haven't even come close to pushing the limits of 2 MB memory on my boards, so your 16 MB seems HUGE to me! *grin*Somewhere in the CF spec is the requirement that nIORD or nIOWR assert 70ns after nCS0 or nCS1 asserts. But the CPM15000.SR image works fine. I was never able to figure out why that wouldn't work. The output of the DTACK gates nIORD or nIOWR thus giving it a delay of 70ns after the assertion of CF chip select. I meet the timing spec with one wait state when accessing CF. After that nCS0 or nCS1 may negate and address change. The design file is here but the logic is scattered over two sheets.
0 Comments
Leave a Reply. |
AuthorRussell ArchivesCategories |