Jump to content

User:Skierpage/Windows reinstall: Difference between revisions

From KDE UserBase Wiki
the woes
 
Skierpage (talk | contribs)
m link to Disk recovery page
 
Line 1: Line 1:
After I trashed the first GB of my disk, Windows wouldn't reinstall.  Worse, if I booted from my Windows XP CD-ROM, which amazingly I managed to find, it would not acknowledge the existence of my drive.
After I trashed the first GB of my disk, Windows wouldn't reinstall.  Worse, if I booted from my Windows XP CD-ROM, which amazingly I managed to find, it would not acknowledge the existence of my drive.


== Windows XP can't boot lots of hardware, eve old hardware!!!! ==
== Windows XP can't boot lots of hardware, even old hardware!!!! ==
 
I thought this was because I had trashed the disk so badly, so I spent a lot of time backing up the Windows partition to a hard drive, running repair tools, etc.


I thought this was because I had trashed the disk so badly, so I spent a lot of time backing up the Windows partition to a hard drive, running repair tools, etc.  (I ran these [[../Disk recovery]] tools from my Kubuntu live CD, the bootable recovery console on the Windows CD is a pathetic joke in comparison.)


== Windows XP doesn't recognize SATA drives! ==
== Windows XP doesn't recognize SATA drives! ==
Disk corruption wasn't the problem.  XP can't see my disk because it simply doesn't support SATA drives.
But it turns out disk corruption wasn't the problem.  XP can't see my disk because it simply doesn't support SATA drives.


So I spent time building a newer "slipstreamed" XP boot CD-ROM, incorporating the MS XP updates.  Of course, unlike Linux vendors that love people booting their operating system on any and all hardware, Microsoft hates the idea of you making a bootable Windows, they want you stuck with the 5 year-old CD-ROM with the holographic logo.
So I spent time building a newer "slipstreamed" XP boot CD-ROM, incorporating the MS XP updates.  Of course, unlike Linux vendors that love people booting their operating system on any and all hardware, Microsoft hates the idea of you making a bootable Windows, they want you stuck with the 5 year-old CD-ROM with the holographic logo.

Latest revision as of 06:16, 16 April 2010

After I trashed the first GB of my disk, Windows wouldn't reinstall. Worse, if I booted from my Windows XP CD-ROM, which amazingly I managed to find, it would not acknowledge the existence of my drive.

Windows XP can't boot lots of hardware, even old hardware!!!!

I thought this was because I had trashed the disk so badly, so I spent a lot of time backing up the Windows partition to a hard drive, running repair tools, etc. (I ran these User:Skierpage/Disk recovery tools from my Kubuntu live CD, the bootable recovery console on the Windows CD is a pathetic joke in comparison.)

Windows XP doesn't recognize SATA drives!

But it turns out disk corruption wasn't the problem. XP can't see my disk because it simply doesn't support SATA drives.

So I spent time building a newer "slipstreamed" XP boot CD-ROM, incorporating the MS XP updates. Of course, unlike Linux vendors that love people booting their operating system on any and all hardware, Microsoft hates the idea of you making a bootable Windows, they want you stuck with the 5 year-old CD-ROM with the holographic logo.

I had lots of problems doing this (see #nLite woes, discussed on the nLite/msfn forum http://www.msfn.org/board/cd-key-issue-xp-sp3-build-t136123-page-20.html

That didn't help. Even newer XPs just don't notice the hardware. Bastards.

Microsoft's approach to this is "Press F6 to interrupt booting and insert your manufacturer's floppy disk containing drivers. Even though my PC has a floppy disk drive, this is a f***ing nightmare:

  1. even in 1994, no manufacturer supplied floppy disks
  2. manufacturers instead provide huge multimegabyte programs to create floppy disks. Again, the ability to create a bootable disk or one that does something is considered highly valuable secret knowledge that must be hidden, rather than a simple "driver installer" package
  3. but those programs only run on Windows. I'm trying to start Windows! And unlike the unbelievable complete full-featured desktop on a Linux bootable CD, my Windows XP boot disk is ridiculously limited crap (because if it was any good, people would boot the CD, use the temporary Windows, and never complete the install)

So I had to "slipstream" the VIA motherboard SATA drivers. nLite can do this too, but it's very hit or miss.

Anyway, I finally built a Windows XP boot CD slipstreamed to Windows XP Service Pack 3 with the VIA SATA drivesr.

This booted! This recognized my hard drive! I was able to run chkdsk in the recovery console! I was able to run a repair install of Windows XP to my drive! Hallelujah!

Not so fast... After restarting, booting into Windows XP and entering my CD key (which I still had, taped to my Northwest Falcon binder), I had password errors.

nLite woes

I ran nLite on a Vista laptop to build new Windows boot CDs. These seemed to work, but they had this error.

Basically, you can't run nLite on Vista. Even though "all" it does is build a new CD-ROM from a legitimate Windows XP CD-ROM and Microsoft's own updates, it requires OS support that breaks between operating systems.

So I have to have a working XP to install. But my PC won't boot Windows.

Virtual Machine to the rescue

I installed Virtual Box 3, created a Win XP virtual machine, ran nLite in that, tested the .iso by making it the virtual machine's CD-ROM and repairing the virtual machine (that blew my fragile little mind), then burned the .iso to CD-RW and... it worked to repair my actual XP partition! thumbup.gif

Finally booting!

So at last I could boot into Windows XP. Some missing files, lots of updates, lots of missing bits and pieces.

The problems included:

Thunderbird woes

Nothing in C:\Documents and Settings\S Page\Local Settings\Application Data\Thunderbird\Profiles\1y6g4zic.default

so I copied everything from \\space\spage\spage559_Docs_Settings\S Page\Application Data\Thunderbird\Profiles\1y6g4zic.default , dated around 10/30/2008.

Start up errors

On most start-ups, Windows XP thinks it has to check C: for errors

Upon login as skierpage,

  • I get a window (or error?) from ATI\ATICUS~1\ATICUS~1.EXE.
  • I get one o more "Send error report?" dialogs. If I allow, my browser goes to"Blue screen error caused by a device or driver".


Can't Standby!

Start > Turn Off Computer > Standby is grayed out!

ATI/Uninstall errors

In desktop menu, "[ATI logo] Catalyst(TM) Control Center" does nothing.

In desktop menu > Properties > Settings > Advanced > Adapter , "Adapter Type" is empty, and everything under Adapter Information (Chip Type, DAC Type, Memory Size, etc.) is "<unavailable>"

When I run any of the ATI driver setup programs in C:\Falcon\Drivers\Video\ATI , the program silently exits.

I had problems with InstallShield uninstall directory somewhere, so I deleted it. Now uninstalls don't work.

In Start > Control Panel > Administrative Tools > Event Viewer, MTC service fails to start.


ATI Uninstalls

Add/Remove Programs:

* ATI Catalyst Control Center [Change/Remove] gives

RUNDLL "Error loading C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\09\01\Intel32\Ctor.dll"

* ATI Catalyst Registration, clicking [Remove] gives Windows Installer error about "resource... unavailable"

C:\DOCUME~1\SPAGE~1\LOCALS~1\Temp\_is9952\

* ATI - Software Uninstall Utility [Change/Remove] "Completely remove all ATI/AMD (Graphics/Chipset) software" option gives:

Please wait then RUNDLL "Error loading C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\09\01\Intel32\Ctor.dll" then Please wait then Guide Plus+ for Windows "Error extracting support files: Access is denied."

All it seems to do is remove registry keys for ATI.

After copying saved C:\Program Files\Common Files\InstallShield, still has problems removing

  • ATI CCC (some missing data2.ca
  • ATI Catal
  • ATI Remote Wonder Error

"Error 1905.Module C:\Program Files\ATI Multimedia\RemCtrl\ATIRW.DLL failed to unregister. HRESULT -2147220472. Contact your support personnel." "(much the same, different DLL)" "Error 1905.Module C:\Program Files\ATI Multimedia\RemCtrl\Plug-Ins\GemstarRmtPgn.dll failed to unregister. HRESULT -2147220472. Contact your support personnel." "Error 1905.Module C:\Program Files\ATI Multimedia\RemCtrl\Plug-Ins\PowerPoint.dll failed to unregister. HRESULT -2147220472. Contact your support personnel." "Error 1905.Module C:\Program Files\ATI Multimedia\RemCtrl\Plug-Ins\WinAmp.dll failed to unregister. HRESULT -2147220472. Contact your support personnel." "Error 1905.Module C:\Program Files\ATI Multimedia\RemCtrl\Plug-Ins\MLRmtPgn.dll failed to unregister. HRESULT -2147220472. Contact your support personnel." "Error 1905.Module C:\Windows\system32\ATIRWRF.DLL failed to unregister. HRESULT -2147220472. Contact your support personnel." "Error 1905.Module C:\Windows\system32\ATIRWRF.DLL failed to unregister. HRESULT -2147220472. Contact your support personnel."

Was able to remove

Programs > GUIDE PLUS+ > GUIDE PLUS+(TM) System Update Wizard - ATI eventually failed to update patch...

After reboot

Running C:\Falcon\Drivers\Video\ATI\9_3_xp32_dd_ccc_wdm_enu\ Setup.exe still gave me choice to install two tiny drivers, still exited early on.

I was able to run the nested CCC Setup.exe program. Apart from complaining about a mismatched install.ini in C:\Program Files\ATI Technologies\ATI Catalyst Control Center (which it put there!), it seemed to install.

Ran C:\Falcon\Drivers\Video\ATI\9_3_xp32_dd_ccc_wdm_enu\Driver\AtiCimUn.exe and that

  • uninstalled DAO
  • configured (removed?) the ATI Catalyst Control Center I just installed
  • Ran InstallShield for GUIDE PLUS+, but got "Error extracting support file: Access is denied."

I just couldn't get past this so I deleted C:\Program Files\Gemstar myself.

In Safe Mode

In fact I'm running VGASafe (save?) weird video driver.

Couldn't install ATI_dd (driver only), it complained about no DirectX. Went through detailed instructions for trashing all remnants of ATI drivers, rebooted, didn't help...

VGASave -- no drivers!!!

I searched for this and found a note at Wolfxxx site about missing motherboard drivers. That might explain why I had no AGP in Device Manager and no Video either!

I should have checked more closely against drivers in C:\Falcon\Drivers\Motherboard\AMD\VIA\ downloaded VIA_HyperionPro_V524A driver package:

Update INF Files of VIA chipsets to load proper system drivers
VIA AGP Driver 4.60A
The AGP interface provides a fast connection between the core-logic and the graphics controller without using PCI bus bandwidth.
VIA PATA/SATA IDE Driver Package V2.80A
VIA PATA/SATA IDE Controller Driver
VIA V-RAID Driver Package V5.80a
VIA V-RAID Software for VIA RAID Controller
VIA V-RAID Config Utility V5.85
VIA V-RAID Config and Monitor Utility

Allowed some V-RAID thing to run at each windows startup (??)

vs. my drivers in C:\WINDOWS\system32\drivers

  • viaagp.sys VIA NT AGP Filter v 5.1.2600.5512 2008-04-14
  • viaide.sys Generic PCI IDE Bus Driver v 1.0.1.1 2008-04-14
  • viamraid.sys VIA AHCI RAID DRIVER FOR WIN XP/SRV2003 5.1.6000.581 2009-07-26
  • viasraid.sys VIA SATA RAID DRIVER FOR WIN XP 5.1.2600.210 2003-05-09



Other items in Add or Remove Programs

Removed Apple Mobile Device Support and Bonjour

?!? Why two "DAO" installs? This is something ATI installs.

I downloaded msicuu2.exe, "Windows Install Cleanup". Much to clean up...

  • all the old Javas I deleted
  • one of the two "DAO"s.

I had Google Updater errors, but I ran it and was able to update Picasa and Skype OK.

Event Viewer errors

I ws getting lots of errors from some MTC thingy.

2009-08-03 in System,

  • one:

The EMS Inter-Link driver V3.0 service failed to start due to the following error:

  • lots of:

The Application Management service terminated with the following error: The specified module could not be found.


Try to fix video woes - DISASTER

ATI wouldn't install, it didn't recognize its own card.

Again, more %&*$#@! driver crap. Windows XP doesn't seem to have the necessary drivers to see an AGP video card. It can talk basic video to it, but ATI's own installer doesn't see the card.

So I somehow installed a bunch more VIA AGP drivers.

Now my PC won't boot into Windows again! ARGHHHHHH