"Real" windows boot CD
Posted 08 July 2002 - 07:58 PM
My problem is that I want to make a true windows boot CD to solve a number of problems, but mainly how to backup my notebook drive (I use partitionquest drive image) to an external HDD connected via Firewire. normally PQDI boots to DOS to do the backup, and of course there is no DOS support for firewire. For partition othere than the active windows, PQDI will run under windows. and there use the drivers. So if i can just boot windows from the CD . . . .
I cannot beleive no-one else wants to do this !
Posted 08 July 2002 - 11:38 PM
I currently try to get figured out, if there is a possibillity to also make NT/2K or XP bootable from CD - maybe like ERD Commander!
Posted 09 July 2002 - 03:00 AM
Posted 11 July 2002 - 04:00 AM
What can be the problem? To much memory (1,5 Gb)?
Posted 17 July 2002 - 03:58 AM
Could it be that some of the things you run/install autoexec or config.sys or windows.whatever) need to write to the disk?
There is hardly any self-modification going on (although I wouldn't put it past MS), but some progs. and drivers need to do some temp stuff, which they just might do in the current directory (which, in the case of a bootable CD, would be read-only!!!)
Have you tried some kind of ram-disk trick?
Please let me know if you succeed in this undertaking, I would be VERY interrested in obtaining a copy of such a CD image!!! (Even one booting DOS would be nice).
Posted 17 July 2002 - 06:23 AM
Posted 17 July 2002 - 02:03 PM
Posted 19 July 2002 - 01:34 AM
So at that stage all you have done is installing W9x on your X: hardrive using subst.exe (c:wsubst.exe x: c:cdrom)
The ram-disk trick comes later when w9x is installed and you have all your modifications and applications up and running
Posted 19 July 2002 - 01:38 AM
The article in question is translated from german. My german is not so good, but maybe something got lost in the translation.
I would still like to get past the memory error after the first reboot in the installation process.
Posted 19 July 2002 - 09:30 AM
Posted 19 July 2002 - 06:00 PM
Posted 20 July 2002 - 09:10 AM
1. Make sure your paths are correct "c:w..."
2. Make sure you load Himem.sys as the first line of you config.sys file
3. Make sure you load all drivers with DEVICEHIGH=
4. On autoexec.bat, use the command lh c:wsubst.exe x: c:cdrom
5. Also in autoexec, check you path line - make sure it doesnt read anything extra... shold be
6. Did you install windows "first install process" to x:w?
Make sure of all those things, and it should work, if not, please let me know.
Posted 20 July 2002 - 10:02 AM
I am not sure if it is something in command.com or in io.sys that is creating the problem, if someone has an idea, it would be greatly appreciated, plus, I figure im only like 10 minutes away from actually having a complete version on cd along with a bunch of other apps ...This may be a tech question for Twinkie or so...
Posted 23 July 2002 - 12:17 PM
Posted 24 July 2002 - 04:25 AM
Posted 24 July 2002 - 01:43 PM
Posted 30 July 2002 - 11:28 AM
? ) ?
Posted 31 July 2002 - 02:07 PM
I would love to use this for client temp restores.
Can you access the Internet once it's running? I don't see how any of this is possible.
Posted 01 August 2002 - 07:14 AM