Well you will need a new ldd and sys file as the ones I think you are using have the off by 1 sector problem. You should be able to take the files I am putting together and make a new CF image if a few seconds. And customizing the files on the image is really easy - it is just a matter of using cpmcp as the copy utility to copy files from you PC into the CPM image file. I will have this all Documented hopefully by the end of the weekend - and David Fry will be my second pair of eyes to keep me honest :)
Dave On Wednesday, June 18, 2014 2:58:42 PM UTC-5, Thomas Owen wrote: > > Hi David, > > well this is good news and I look forward to seeing what changes you > made. Will I need to generate a new ldr and sys and simply place them on > the CF? > > Thanks, > Thomas > > > On Wednesday, June 18, 2014 2:29:25 PM UTC-4, David Fry wrote: >> >> Hi Dave, John >> >> just a quick update from me. >> I have grabbed a few hours over the last couple of days to update the >> disk format to comply with cpmtools. >> the changes are very minor, basically only the removal of one line of >> code (decrements LBA value by one) in each instance of the wrlba routine, >> this change >> also removes the need for a modified MYIDEROM to serve as a boot >> platform, the CF disk can now boot directly from a S100 Z80 Monitor (option >> 'P'). >> I have started to update my documentation and remove obsolete >> information, hoping to have this completed by the end of the weekend when I >> wil upload a new ZIP file to my N8VEM folder and take down the old one. >> >> The screenshot below shows the working CPM3 image, the files are as >> supplied in the CPM3 distro from http://www.cpm.z80.de/ >> The disk image was created using a combination of old and new methods, >> The Altair sim was used to create CPMLDR.COM and CPM3.SYS and these were >> placed into the disk image using the old method of sector copying. All the >> other files were copied into the disk image using cpmtools, the result >> being checked in a hex editor and all looks good. >> >> one step closer to simplifying the process :-) >> >> regards >> >> David Fry >> On Saturday, June 14, 2014 5:31:49 PM UTC+1, monahanz wrote: >> >>> Guys, it’s great to see all the progress and uptake this simple little >>> IDE board has generated. Thomas in particular congratulations on >>> putting so much time and effort into “hammering into shape” the process for >>> first time installs. It helps tremendously but I think it will still >>> be difficult for some people to do. We all should remember how it was >>> when we first started! >>> >>> >>> >>> I’m wondering if somebody out there could spend the time writing a >>> PC/MSDOS based program to setup a CF card for first time users. If we >>> agree the IDE board ports start at 30H, the only variable would be the >>> console I/O. This could be either spliced into the final disk image >>> with the above program (leaving room in the base code with NOP’s) or by >>> answering a Q&A session and inserting code like the old XMODEM programs >>> did. >>> A CF card is laid down as Dave describes and is checked out. Once the >>> image is laid down it can be dumped sector for sector any CF card (no >>> holes of course). The image can even include a few CPM programs. Probably >>> best to start with a non-banked CPM3 image. This program would run on >>> a standard PC, format the CF card and write the image sector by sector. >>> Not sure if Windows 7,8 allows you to do that easily but there must be a >>> way. >>> >>> >>> >>> This would allow anybody not as sophisticated as some of us, to get >>> going right away and allow them to write more elaborate CPM3.SYS files that >>> include a FDC, printer etc. in the BIOS for their own hardware. >>> >>> I think something like this would be a tremendous asset for first time >>> S100 users. >>> >>> >>> >>> Any volunteers? >>> >>> John >>> >>> >>> >>> >>> >> -- You received this message because you are subscribed to the Google Groups "N8VEM-S100" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
