ptpovo
asked on
Major goof with attrib...
I was using NBTSTAT with it's various (-) options then, after reading an article on another subject, switched to my c:\windows directory and absent-mindly began using ATTRIB with its (-) options on the entire directory. Oh dear!!!
Long lists of files scrolled by as I used the -h option. More long lists scrolled by as I used the -s option. I may have even used -r. It was about this time time that I realized my error. I was thinking DIR /A:H, etc...
How can I rebuild the proper file attributes in this directory? I imagine I'll need to use a boot disk and restore my system files one at a time unless someone knows how to do this some other way. Once the Win95B is up and running, I guess I'll have to rebuild file attributes for my apps as they complain about not finding this or that file. Please make suggestions.
I need to restore this workstation asap. Thanks...
Long lists of files scrolled by as I used the -h option. More long lists scrolled by as I used the -s option. I may have even used -r. It was about this time time that I realized my error. I was thinking DIR /A:H, etc...
How can I rebuild the proper file attributes in this directory? I imagine I'll need to use a boot disk and restore my system files one at a time unless someone knows how to do this some other way. Once the Win95B is up and running, I guess I'll have to rebuild file attributes for my apps as they complain about not finding this or that file. Please make suggestions.
I need to restore this workstation asap. Thanks...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
i personally wouldn't worry about it - just leave them be and make sure not to start playing with deltree
i personally wouldn't worry about it - just leave them be and make sure not to start playing with deltree
ASKER
cumbo - I found a similarly configured workstation and typed ATTRIB>LPT1 in the c:\windows directory. I used a boot disk to start up the workstation with the problem, logged in using a netx client and typed ATTRIB>LPT1 in the c:\windows directory. What a mess I made. I chose the slow approach and compared the lists one file at a time making changes where necessary and I now have a my workstation back.
I had already tried the WIN95 setup routine from the flat file on the hard drive but was unable to get past the Product ID screen and I couldn't figure out how to dump the HKEY_LOCAL_MACHINE\SOFTWAR
snowolfe - thanks for the advice...
I had already tried the WIN95 setup routine from the flat file on the hard drive but was unable to get past the Product ID screen and I couldn't figure out how to dump the HKEY_LOCAL_MACHINE\SOFTWAR
snowolfe - thanks for the advice...
ptpovo,
Glad you fixed the problem. Good idea to print the Attrib's and compare.
Slow going tho..When system is up & running you can copy your
product code from the "General" tab under the "System" icon in
Control Panel. Write it down in a safe place.
A handy place to keep reg numbers is in your Autoexec.bat file.
Edit the autoexec.bat file that reads: REM Win 95 Reg code
nnnnn-oem-nnnnnnn-nnnnn. Save the file and copy to a floppy.
Cumbo
Glad you fixed the problem. Good idea to print the Attrib's and compare.
Slow going tho..When system is up & running you can copy your
product code from the "General" tab under the "System" icon in
Control Panel. Write it down in a safe place.
A handy place to keep reg numbers is in your Autoexec.bat file.
Edit the autoexec.bat file that reads: REM Win 95 Reg code
nnnnn-oem-nnnnnnn-nnnnn. Save the file and copy to a floppy.
Cumbo
I currently run a single PC with multiple versions of Windows as a support system for a number of PC users. To make my life easier I have turned off all the system, hidden and read-only attributes in the multiple windows directories and at the DOS level. (Basically, no +s +h or +r setting anywhere in the entire file system,) These attribute settings (or non-settings) do not cause me problems.
So, my suggestion is to leave the attributes alone and continue to run the system as is.
So, my suggestion is to leave the attributes alone and continue to run the system as is.
ASKER
RayFrye, I didn't realize you could remove those attributes, particularly the system flag. The problem I had was that windows wouldn't start. As I later dicovered, numerous files had been inadvertently given a system flag - specifically win.com. Windows complained that it couldn't find this file and refused to proceed. So, in a nutshell, everything will work just fine with no attribute settings, but, if you choose to use them, be sure you use them properly... Thanks for the tip.