|
Forum: EasyBoot Topic: Windows 98 lockups started by: kloudfreak Posted by kloudfreak on Feb. 23 2005,22:32
I've had this problem that I can not find an answer to, and can not find a common thread.I have made several multi-boot cds which have 95-me and nt-xp all multiple types, attended, unattended etc. The problem is that when making a Windows 98 install image, on some systems 98 will freeze after the initial progress bar goes across the screen (I think it is collecting info) before it asks for any information at all. Taking the same exact files and putting them on a standard bootable cdrom without ezboot, the install runs fine. Some tings I have noticed on this particular issue are: This problem occurs on only some machines It does not occur on virtual machines It occurs on machines that also have the FDISK problem It happens on older machines P3 and earlier..(this may be irrelevant being that newer machines typically don’t get windows 98 on them) It happens on multiple vendor machines (Dell, gateway, HP to name for certain) One machine in particular is a Dell XPS T800 with 128 megs ram (i believe may be 64) All of the other tools (PE, 2k installs, standard dos functions (format copy etc) work fine the actual code used to start the install is:
located in the autoexec.bat file made from a standard 98 bootdisk with default set to start with cdrom support and timeout=0 in config.sys dropping to dos (Shift+F5) from windows 98 boot disk in EZboot and then typing setup, setup /im or setup /C all give the same problems this almost seems to be a conventional memory problem...possibly ezboot is not exiting completely or having a true clean boot to an image file. The alternative that we have found on these type of systems is to use a standard boot disk w/o ezboot to load 98. This is not a problem with the CD or the load of 98 itself, as the same exact CD on a different computer will work fine (fdisk also works fine on 2nd computer) Any help on this will be appreciated. I have not found a problem with any other OS's .. although I feel 95 and ME will also have the same problem (we don't install Me on systems, and no longer support 95). The Fdisk is the other main problem, as it can detect errors on hard drives in different ways than programs like gdisk can. Posted by Incroyable HULK on Feb. 24 2005,08:31
I'm not sure this can help but have you took a look at this Multi-Boot guide? < http://flyakite.msfnhosting.com/ > It is written with CDSHELL in mind but it is the same concept as using EasyBoot... Posted by kloudfreak on Feb. 24 2005,15:49
any other boot managewr will work fine. ....diskemu etc...there are just some featuires i prefer with ezboot, that i woudl like to just keep with it. like i said, this is the only issue i have with it, so dont want to have change everything just based on oen problem Posted by kloudfreak on Mar. 01 2005,14:10
no takers?
|