Recent Articles
Securing your Wireless LAN
Wednesday, August 18, 2010
Some tips and things you might not know about your wireless network.
Handling a Subversion Repository URL Change
Sunday, May 3, 2009
If your repository URL changes, you can use the following command to fix existing snapshots.
vfat Mounts Default to Lowercase Shortnames
Tuesday, April 21, 2009
I want a "this is brain-damage" quote from Linus for this mess.
VirtualBox or VMWare Virtual Machine at Login
Sunday, April 12, 2009
How to start a virtual machine in X when a user logs in.
Dialog Progress Bar Through Pipe
Sunday, April 12, 2009
How to use dialog to display a script progress bar and communicate progress to it through a named pipe.
Never argue with a fool, people might not know the difference.
Sys Admin
Windows...Filesystem...
First of all, if you can move the hard drive to another computer that is your best bet. Move it to another working computer and run scandisk/chkdisk on it and try to repair it. If anything get it to where you can get anything you want off of it.
In my case, the operating system is installed on a Raid 5 array behind an Adaptec controller so there is no moving this to another computer. The problem I was having is a blue screen half way through Windows 2000 startup which I determined was most likely the result of filesystem corruption. The blue screen was a 0x24 in ntfs.sys.
The first thing you can try is running the Recovery Console. Now, this becomes an issue because you need to run Windows 2000 setup which tries to load any NTFS filesystems at "Starting Windows 2000." You'll most likely get the blue screen here also. To stop Windows from trying to load the corrupt NTFS filesystem, create the 4 boot disks and modify the first boot disk. Comment the line "ntfs=ntfs.sys" in the txtsetup.sif file on the first setup disk. This allowed it successfully to make it to the setup screen. Make sure and press F6 at the beginning of Windows 2000 setup if you need to specify any additional hard drive drivers, as in my case.
Once at the setup screen, press F10 to go into the Recovery Console. You want to make sure you don't run dir here. You'll most likely get a blue screen and you don't have any NTFS filesystems loaded anyway. Simply run chkdsk c: /p at the RC command prompt and the exit to reboot. The chkdsk utility has its own NTFS support and does not require the ntfs.sys driver that we stopped from loading.
If that doesn't work, your next option is to stick in another disk (preferably some IDE disk) and install Windows 2000 to that. Then, you can hopefully try and repair the corrupt disk from within Windows 2000 with the normal Windows utilities or some other utility. When you are done you can remove the temporary disk and change the boot disk back to the once corrupted disk.
Adaptec AR0-1130C Raid Controller Setup and Configuration
Convert Windows 2000 BDC to PDC After PDC Failure
msconfig Utility
Domain Logon Scripting
Network Speed Tester (win32)
Windows...Filesystem...Filesystem Corruption Booting Windows 2000 0x24 Blue Screen
Saturday, September 4, 2004 by digitalpeer
In my case, the operating system is installed on a Raid 5 array behind an Adaptec controller so there is no moving this to another computer. The problem I was having is a blue screen half way through Windows 2000 startup which I determined was most likely the result of filesystem corruption. The blue screen was a 0x24 in ntfs.sys.
The first thing you can try is running the Recovery Console. Now, this becomes an issue because you need to run Windows 2000 setup which tries to load any NTFS filesystems at "Starting Windows 2000." You'll most likely get the blue screen here also. To stop Windows from trying to load the corrupt NTFS filesystem, create the 4 boot disks and modify the first boot disk. Comment the line "ntfs=ntfs.sys" in the txtsetup.sif file on the first setup disk. This allowed it successfully to make it to the setup screen. Make sure and press F6 at the beginning of Windows 2000 setup if you need to specify any additional hard drive drivers, as in my case.
Once at the setup screen, press F10 to go into the Recovery Console. You want to make sure you don't run dir here. You'll most likely get a blue screen and you don't have any NTFS filesystems loaded anyway. Simply run chkdsk c: /p at the RC command prompt and the exit to reboot. The chkdsk utility has its own NTFS support and does not require the ntfs.sys driver that we stopped from loading.
If that doesn't work, your next option is to stick in another disk (preferably some IDE disk) and install Windows 2000 to that. Then, you can hopefully try and repair the corrupt disk from within Windows 2000 with the normal Windows utilities or some other utility. When you are done you can remove the temporary disk and change the boot disk back to the once corrupted disk.
Related Local Pages
Windows 2000 Disk Larger than 128GBAdaptec AR0-1130C Raid Controller Setup and Configuration
Convert Windows 2000 BDC to PDC After PDC Failure
msconfig Utility
Domain Logon Scripting
Network Speed Tester (win32)
Comment Monday, November 29, 2004 by
Steve Owen
I can't tell you how much I appreciate the information in this article. I was ready to give up the array after many frustrating hours and attempts to get Windows setup and other boot disks to work. I followed your instructions and was able to save the data on our Exchange server and repair the corruption. Thanks again (said with a sigh of relief at 2:45 a.m..)!!
Comment Friday, May 2, 2008 by
AIRMAN
I also was close to give up the hd and the personal data on it. So a big thanks to the author of this article who prevent me from a lot more pain and lost data.
cheers from cologne - AIRMAN
cheers from cologne - AIRMAN
