Frogboy Frogboy

ATT: ALL WINDOWS 98/ME USERS

▼

ATT: ALL WINDOWS 98/ME USERS

from Stardock Forums
Okay, we've found a glitch in the Stardock Central Installer that can cause deletion of files that shouldn't be deleted.

So if you're using Win98/ME, hold off on downloading/installing Stardock Central. We'll have this fixed in a few minutes.
2,047 views 65 replies
Reply #51 from Stardock Forums Top
Thanks Horatio!
Reply #52 from Stardock Forums Top
On W2K, I was also missing NTLDR and NTDETECT.COM and boot.ini after SDC 0.99; copied NTLDR and NTDETECT.COM from my \I386, but no backup of boot.ini. Good thing I don't reboot every day.

~SDC~
Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #53 from Stardock Forums Top
Create a text file, rename to boot.ini, paste this in, save and try it

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
Reply #55 from Stardock Forums Top
Well, I had downloaded SDC to prepare to download GalCiv tommorow.
Saw this warning and checked my /c: drive and saw some files and decided to restart to make sure it still worked. got a message right before my desktop popped up "invalid boot.ini file" but then windows started up as usual. Should I be worried about anything?

~SDC~
Reply #56 from Stardock Forums Top
You're apparently okay but you'll want to get a new boot.ini.

Here's directions on how to do that courtesy of trav:

Create a text file, rename to boot.ini, paste this in, save and try it

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
Reply #57 from Stardock Forums Top
No, thats fine. It just means the syntax is screwy in it.

Basically the boot.ini is a file that tells the computer where to look to start up. Your old version and new version are slightly different. If it boots, just be happy. If it bugs you that much, I can try and see what exactly is wrong with it.

~SDC~
Reply #58 from Stardock Forums Top
Hi there,

ok, I installed the SDCentral Client yesterday (Win XP Pro) but didn't have any Problem at all.

Don't know if it means anything, but I installes it on a different partition than the OS is residing on.

And a comment regarding the boot.ini:
Mentioned suggestions (recovering from another machine, or writing a new one as pasted above) will only work if the system was installed on a comparable partition/hdd configuration, as NT/2K/XP numbers the harddisks and partitions according to IDE channel (or SCSI ID) and partition depending on the configuration.

cya
DocDVD
Reply #60 from Stardock Forums Top
Frogboy,

The boot.ini is just from a basic W2K install, not sure if it will work for XP. My Boot.ini file looks like this for XP Pro, generic install.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


~SDC~
Reply #61 from Stardock Forums Top
/Shrug. Made the boot.ini file as was listed for WinXP and still got the invalid boo.ini message. The exact message was,

Invalid boot.ini
booting from /WINDOWS

So I guess its not that big a deal.

Thanks for the help :D

~SDC~
Reply #62 from Stardock Forums Top
Hi there!

I'm having a similar problem.

I'm running XP home, and the ntldr files in c:\ are NOT missing. I thought everything was okay, but the computer failed on reboot. I get a message stating that the file C:\windows\system32\hal.dll is missing. I'll try the XP recover suggestions above when I get home tonight, but I don't see the hal.dll error mentioned.
Reply #63 from Stardock Forums Top
its only v0.99 that does this, it wiped 70% of my hard drive, v0.98 works like a charm though
Reply #65 from Stardock Forums Top
Well, I got burned last night, and had to use my restore disk. (Wuindows ME)

Unfortunately, it reformats and reinstalls.



~SDC~