Frogboy Frogboy

For Beta testers: SDCentral Issue Update

For Beta testers: SDCentral Issue Update

On Sunday/Monday, Stardock released a new stand alone build of Stardock Central. The installer of this build had a defect that, on some systems, could erase files from the c:\ directory.

If you have installed version 0.99 of Stardock Central, check your c:\ to ensure that there are files still there. If files have been erased, follow the instructions below to recover.
Print this out before continuing.

Windows XP:
1.
copy c:\windows\servicepackfiles\i386\ntldr c:\
copy c:\windows\servicepackfiles\i386\ntdetect.com c:\
copy a:\boot.ini c:\

2. Insert your Windows XP CD into the CD-Rom drive and reboot. When the installer comes up, you may need to press F6 and insert a driver disk if your OS is installed on a fast-ata drive.

3. Once the installer is running, choose to repair using the recovery
console.
4. Choose your installation (1 for a single-boot machine)
5. When the recovery console appears, place the floppy with the
extracted files in the drive and type "copy a:\*.* c:\.


Windows 98/ME

http://www.stardock.com/temp/win_98_org_root.zip Windows 98 Original
http://www.stardock.com/temp/win_98_se_root.zip Windows 98 SE
http://www.stardock.com/temp/win_me_root.zip Windows ME

1. Unzip the appropriate files to your c:\ drive.

2. We've tested the above solution here, but there's a chance we've missed something. If that is the case, you can download a full boot disk for the appropriate platform from
http://www.bootdisk.com/original.htm. Boot off that, exit to a command prompt (should be in the root of the a: drive), and then type "sys c:" to update the system back on the drive.

Windows 2000:
1. Extract the contents of http://www.stardock.com/temp/win2000_root.zip
to a blank floppy. You can also try unzipping these to your c:\ drive.

If the system cannot boot up, go to the next step. Step 1 should work though in most cases.

2. Insert your Windows 2000 CD into the CD-Rom drive and reboot. When the installer comes up, you may need to press F6 and insert a driver disk if your OS is installed on a fast-ata drive.

3. Once the installer is running, choose the R option to repair. If you have an emergency repair disk handy, follow the path to use that. If not, select the recovery console option.

4. With the recovery console option, place the floppy with the extracted files in the drive and type "copy a:\*.* c:\".
2,000 views 29 replies
Reply #26 Top
I had already set my system to show hidden files, but I can't see the three files identified in the thread. However, when I tried to rename a backup of boot.ini in the c:/ directory, it would not let me because there was already a file with that name. I guess that means nothing was deleted, but I would like to make sure before I reboot.

Since I downloaded under the SDC version that was updated (or maybe backdated) in response to this problem, the deletion should not have occurred. On the other hand, I would like to verify for certain that it did not occur.
Reply #27 Top
Just because you made them visible is not the same as showing 'system files', thats a seperate option on some versions of Windows.
Reply #28 Top
I did both. The hidden files option had already been selected. I still don't see those three files, but if the boot.ini file did not exist, it should have let me rename the backup in that directory.

~SDC~
Reply #29 Top
bump (for those who had downloaded the bad beta prior to release)