It looks like you're new here. If you want to get involved, click one of these buttons!
So, I advice you not to use pure NT3.1WS. Use Hybrid instead...
Good idea, but will it work correctly with newer NTs... like XP and 2k?
Several CDS or one or maybe two dvd's seems most appropriate...
Actually, I just realized something - since one is going to have to lay out the CD, why not just build a list of OSes present *before burning*? The mastering program would also to have to be a frontend to mkisofs. The DOS program would simply read the data that the masterer outputs.
But NT 3.1 Hybrid is much better than original cuz the original one has tons of missing crap, and so on...
Actually...yes. You just have to lay out the CD in a specific manner. AFAIK, they don't mind being started from DOS.
Nov. 15, 2004
I've been working on the menu on and off since Saturday. It's written in VB4/16-bit and runs on Mini-Windows. So far, I've been working on what is probably the hardest part of development: the modularity. Right now, I have it scanning by group of OS (DOS, really old, 9x, old Nt, new NT). Now, I need to implement per-OS scanning. I can use mostly the same code. However, after about 45 minutes or so of coding each day, I hit a kind of "coder's block" - I can't code. I can put stuff in, but it doesn't make sense in my mind. So, I won't be working on this again until tomorrow afternoon, but from then, it will be relatively quick. I have yet to move into VMware and actually develop under MiniWin. This will enable me to test in a mostly realistic environment. When I get it wokring off of the emulated HD, I can compress it into the cab and build the CD. Speaking of the CD, I'll use the Win98 startup disk. This will load SCSI drivers and I will place the WinCD cab inplace of EDB.CAB, and automagically start the menu after startup. Full documentation will be included on how to produce your own CD.
PS. OMFG ANOTHER NJER!