Somebody did some cleanup in C:\Windows....

- Collapse -

Re:Somebody did some cleanup in C:\Windows....

by Bob G Dec 12, 2003 1:59PM PST

The Compaq Restore CD has two options so you can do some restoring without losing any programs or data.
There is also a way that the Windows system files can be restored, Compaq support talked me through it a few years ago, maybe some one else has the info. Try the limited restore and see if you can get Windows running. Then use SFC (system file check} to find out what else is missing. Unless the current system files have been backed up you will have problems restoring the system. My system updated files, those not on the restore CD, total about 60 megs. A full restore my be the easiest path.
Bob G

- Collapse -

That's one reason for my concern....

by Keith Marcotte Dec 12, 2003 2:20PM PST

She doesn't have a restore CD - she has the full MS Windows 95 CD. I have no idea whether the CD even came with this PC (she received it from son-in-law). I thought SFC was Win98... If it's Win95, it's one of the files that her son deleted.

- Collapse -

Re:SFC is a WIN 98 program.

by Bob G Dec 12, 2003 11:12PM PST

All my comments relate to a Windows 98 system. I did not see anything in your 1st post to indicate it was a Win 95 system.
Bob G

- Collapse -

Better get your eyes checked Bob :-)

by Keith Marcotte Dec 13, 2003 12:36AM PST

After all the times that I've asked for the info, you don't think I'd forget it in a post of my own, do you?

And a change in plans - child with flu doesn't mix with visit to Grandma...

- Collapse -

PART I.

by Cursorcowboy Dec 12, 2003 9:55PM PST

Win95 may not in some cases detect disk management software and may overwrite the master boot record (MBR) information. Refer to the documentation for the disk management software you are using for information about restoring the MBR.

Also, check the Setuplog.txt file for the following statement:

FSLog: BIOS Heads=:64:, BootPart Heads=:64:

The number above (64 in this example) may vary from computer to computer. If these two numbers are different, replace the system files on your hard disk according to the instructions below.

CAUTION: If you are using Disk Manager or any other disk drive overlay program on a hard disk, make sure that the overlay driver is loaded before you use the SYS command on a hard disk. If the overlay driver is not loaded and you use the SYS command on the hard disk, the drive may not be recognized as being partitioned by the disk drive overlay program and you could experience a data loss or inability to boot from the drive.

Supplemental reading: Cannot Start Windows 95 After Using the SYS Command (Q149110).

- Collapse -

PART II.

by Cursorcowboy Dec 12, 2003 10:00PM PST

Windows may not in some cases detect disk management software and may overwrite the master boot record (MBR) information. Refer to the documentation for the disk management software you are using for information about restoring the MBR.

Major caveats:

a. The MS-DOS Fdisk utility usually updates the master boot record ONLY if no master boot record existed previously. Repartitioning with Fdisk does not rewrite this information.

b. Fdisk has an undocumented parameter called /MBR that causes it to write the master boot record to the hard disk without altering the partition table information. /CMBR re-writes the MBR of the secondary drive (if present) based on the current disk structure. These switches can be used to repair a Master Boot Record that has been corrupted or damaged.

WARNING: Writing the master boot record to the hard disk in this manner can make certain hard disks partitioned with EZDrive/SpeedStor unusable. It can also cause problems for some dual-boot programs and disks with more than four partitions. FDISK /MBR Rewrites the Master Boot Record - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q69013

How to Tell If Drive Overlay Program Is Installed in Windows - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q186057

- Collapse -

Re:PART III.

by Cursorcowboy Dec 12, 2003 10:14PM PST

Read the (hidden) SETUPLOG.TXT file located in the root directory. Setup reads the SETUPLOG.TXT file in the boot root to see if Setup failed previously. If Setup did fail, it prompts you to run Smart Recovery or to continue using the Full Install option. The last line in this file should end with "COMPLETE".

If this file has "COMPLETE" and Setup is run from the same version of Windows, Setup provides a "Verify" option. Using this option causes Setup to check the Windows file sizes and dates. If a file is damaged or missing, it is reinstalled.

Note: When viewing this file and COMPLETE is not indicated, check to see if there is a SETUPLOG.OLD. It may be that you started Setup previously and for some reason cancelled it. This would cause a subsequent SETUPLOG.TXT file to be incomplete. If this is so, exchange names on these two files or delete the x.TXT file and rename the x.OLD to x.TXT.

To use Safe Recovery if Setup failed previously:

1. Run Windows 95 Setup from Win95 (CP | Add/Remove Programs | Install), or from the MS-DOS prompt by changing to the Win95 folder on the CD and typing Setup.

2. When the Safe Recovery screen appears, click Safe Recovery.

Note: There are certain setting which are not retained when using Safe Recovery. See MSKB document located at URL http://support.microsoft.com/default.aspx?scid=kb;en-us;Q140905

3. The restore option includes the choices to "Restore Windows Files" that have changed or are corrupted, or to "Copy all Windows Files Again". Choosing, "Restore Windows Files", replaces only files that are missing or have changed since the last time you ran Setup. Choosing, "Copy all Windows Files Again", replaces all files and allows you to change the installation folder. Choose "Typical' on the next screen.

- Collapse -

Re:PART IV.

by Cursorcowboy Dec 12, 2003 10:16PM PST

Note: Anytime that Win95 Setup is run, the 'System.1st' Registry file (boot root) is also updated. If you are running Setup because of Registry errors there is always the chance that those same errors will progress to the NEW System.1st file. You may want to rename a known good current 'System.1st' file before running Setup so it is not overwritten.

4. Caveats: (Several changes made to the current Win95 environment)

a. Certain items in the Configuration files (Autoexec, Dosstart, and Config) may be "Remed", changed in some manner, or information added.

b. Certain Desktop icons may revert to the Win95 default and certain default Desktop icons (Inbox, Network Neighborhood, Recycle Bin) will return, if they had been removed previously.

c. Possible video problems when using 3rd party drivers. During setup, have the video driver disks available or know what folder the new drivers are in on the hard drive. Any third-party screen logos will have to be reset.

d. Possible problems with removable drives and the possibility of needing the disk(s) for their drivers.

e. If a user has made changes to file associations, they will more than likely be changed back to the Windows default.

f. If a user has moved all the x.TXT or x.HLP files that were installed in the Win95 and System folder to a more appropriate location, they or some of them may be reinstalled in their default folder. Also check for backed up files with extensions x.old, x.bak, and x.--

g. If a user has made certain tweeks to the Registry, they may be returned to the Win95 default. Check your notes on Registry edits after Setup finishes.

- Collapse -

Re:PART IV.

by Cursorcowboy Dec 12, 2003 10:17PM PST

h. If the 'Role of the machine' had been changed from Desktop PC to Server in (Control Panel | System | Performance tab | File Systems) the default will return as Desktop PC and the Registry keys for Desktop and Server NameCache will need correcting again. Check the information in this MSKB link to be sure the Typical Role of This Machine caches are the correct values - Incorrect Settings for File System Performance Profiles - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q138012

i. The MSDOS.SYS file is reconfigured during setup. Re-edit to any prior configurations and check the boot root for backed up files that can be removed.

Notes:

1. Before running Setup, it might be advisable to move all the x.GRP files such as Accessories, Desktop, Documents, etc., and the Progman.ini file, to a floppy or some location outside the Windows folder. For further information, see MSKB at this URL: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q133284

2. Verify Mode Setup Asks for Files that Are Already Present - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q132587

3. During a Verify mode Setup, Setup deletes a registry key that contains the list of files that have been installed by Plug and Play. Since the list is empty when Windows sets up the computer's hardware, it does not know whether the driver files should be the default or file which a user installed as appropriate for peripherials. You may experience some problems in this area.

j. If Internet Explorer v4.x or greater has been installed on this computer, it is suggested that it be removed before running Setup.

- Collapse -

Re:PART VI.

by Cursorcowboy Dec 12, 2003 10:18PM PST

k. If virus-protection software is running on your computer when you start the Setup program, you may receive one or more of the following error messages and sometimes your computer may stop responding (hang):

Unexpected DOS Error 5; Setup Initialization Error; Divide overflow; Sharing Violation; Insufficient Memory or Disk Space; Error Reading from Drive A; Cannot Detect setup.exe on Drive A; Unexpected exit, please report this to Microsoft Product Support; or Setup Error 797

Run the virus detection program before you start Setup, disable the virus detection program, restart your computer, and then start the Setup program. After you run the Setup program, re-enable the virus-scanning software and restart your computer to allow the virus software to run normally.

- Collapse -

Thanks Bill...

by Keith Marcotte Dec 13, 2003 1:03AM PST

Lots to review there.

Does anyone know if disk management software will show up on a Belarc report? I suspect it should but the only person that I know that has one installed is Grandma and plans have changed so I'm not visiting her today. I suspect that they don't have disk management software as it is only a 730MB drive.

- Collapse -

Re:Thanks Bill...

by Kees Bakker Dec 13, 2003 2:16AM PST

Is Cursorcowboy Bill Gaston in disguise? Somewhere in Texas, I believe?

- Collapse -

NT -- Yep.

by Cursorcowboy Dec 13, 2003 8:56PM PST

.

- Collapse -

(NT) Let them ask Santaclaus for a larger disk.

by Kees Bakker Dec 13, 2003 2:32AM PST

.

- Collapse -

Then go for it.

by Cursorcowboy Dec 13, 2003 9:17PM PST

1. Boot with the correct Windows Startup Disk/Emergency Boot Disk (EBD) and at the command prompt, issue the following command, and then press Enter:

SYS C: -- Issuing this command transfers the operating system files from the floppy to the hard drive.

2. The undocumented parameter for FDISK called /mbr causes the master boot record to be written without altering the partition table information. Use the following command at the MS-DOS prompt:

fdisk /mbr

- Collapse -

Thanks guys!

by Keith Marcotte Dec 14, 2003 7:09AM PST

sys c:
and then the msdos.sys file needed to be replaced per Q149110 (file from sys command contained only ';SYS'). Happened to have a copy from the kids' PC with me.
Extracted rundll.exe, rundll32.exe and notepad.exe and we were in business!
Applied the Winsock2 patch while I was there. I think their CD drive is on its last legs but that isn't my concern (for the moment).

- Collapse -

Re:Somebody did some cleanup in C:\Windows....

by Kees Bakker Dec 13, 2003 12:50AM PST

I'm afraid this message has nothing to do with Windows, but more with the boot sector or some missing files in the root folder. I should say Windows is only suspect if the message occurs after you see "Starting Windows 98 ..." on the screen.

Boot from a boot diskette (indeed), and check for presence of io.sys and command.com in the root folder (might be hidden files, so attrib is the command to use). A sys-command will replace or create them, and then you would be able to boot into basic MS-DOS from the boot menu. If, of course, no problems with partitions and FAT's exist. Tools to check that: fdisk /stat, chkdsk c: and scandisk c: (all from the boot diskette). To run Windows, at least a msdos.sys should be present also (might be copied from another Windows 98 system, or simply made with edit). And maybe a command.com in the \windows\command folder. I don't expect they are needed to boot into MS-DOS, but I'm not 100% sure. You'll notice.

Anyway, if you can get the system operational in MS-DOS mode you've taken one small step. Then try: cd \windows and start windows with win (which run win.com). It might give a lot of surprises if any essential file is deleted. But let's not take too big steps.

Good luck,

Kees

- Collapse -

Win95 OSR2...

by Keith Marcotte Dec 13, 2003 1:07AM PST

All of those commands sound like they should work on Win95.

- Collapse -

Re:Win95 OSR2...

by Kees Bakker Dec 13, 2003 2:15AM PST

Windows 98 isnt' that different ... It's not XP. But it has an msconfig and, maybe more relevant for you, an sfc, which windows 95 OSR2 don't have.

Kees

- Collapse -

I was relatively sure about msconfig and sfc...

by Keith Marcotte Dec 13, 2003 5:03AM PST

but some of the details about Win95 are getting hazy. Thanks for the help. Will try everything out tonight.

CNET Forums

Other Forums

Forum Info