allen2

Windows server backup does its backup to vhd file and should also take things like the mbr and not only the files like the wim do. Both backups will keep the link to your other drive/application but if you want to restore from bare metal windows server backup is better as it "should" restore also the mbr and the partition table....

Yes you should be able to load the "system" hive located in "C:\windows\system32\config" and then read the values or export settings you need with reg.exe (command line include with xp).

OK here is what the update is doing (it doesn't ask for a reboot): - added registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version] "6.1.7601.17592"=hex(2):25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,77,69,6e,73,78,73,5c,78,38,36,5f,6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,73,65,72,76,69,63,69,6e,67,73,74,61,63,6b,5f,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,5f,36,2e,31,2e,37,36,30,31,2e,31,37,35,39,32,5f,6e,6f,6e,65,5f,30,62,30,65,34,62,34,30,32,35,63,66,34,30,34,39,00, - deleted registry: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version] "6.1.7600.16385"=hex(2):25,53,79,73,74,65,6d,52,6f,6f,74,25,5c,77,69,6e,73,78,73,5c,78,38,36,5f,6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,73,65,72,76,69,63,69,6e,67,73,74,61,63,6b,5f,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,5f,36,2e,31,2e,37,36,30,30,2e,31,36,33,38,35,5f,6e,6f,6e,65,5f,30,39,33,35,62,37,36,63,32,38,39,65,30,66,64,35,00, - modified registry: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CMF\SqmData] "CMFStopTime"=hex(B):40,9d,a0,c3,45,31,cd,01, -added files: C:\Windows\servicing\Packages\Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\servicing\Packages\Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.mum C:\Windows\servicing\Packages\Package_for_KB2533552_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\servicing\Packages\Package_for_KB2533552_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum C:\Windows\servicing\Packages\Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\servicing\Packages\Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.mum C:\Windows\servicing\Sessions\30224771_2298723297.back.xml C:\Windows\servicing\Sessions\30224771_2298723297.xml C:\Windows\servicing\Version\6.1.7601.17592 C:\Windows\servicing\Version\6.1.7601.17592\amd64_installed C:\Windows\servicing\Version\6.1.7601.17592\x86_installed C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_for_KB2533552_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.cat C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\amd64_installed C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\apds.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\apircl.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\apss.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CbsCore.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CbsMsg.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cmiadapter.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cmitrust.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\cmiv2.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\CntrtextInstaller.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\dpx.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\DrUpdate.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\drvstore.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\esscli.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\fastprox.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\GlobalInstallOrder.xml C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\helpcins.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\locdrv.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\mofd.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\mofinstall.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\msdelta.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\mspatcha.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\OEMHelpIns.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\PkgMgr.exe C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\poqexec.exe C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\repdrvfs.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\smiengine.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\smipi.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\SvcIni.exe C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wbemcomn.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wbemcore.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wbemprox.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\WcmTypes.xsd C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wcp.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wdscore.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wmicmiplugin.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wmiutils.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\wrpint.dll C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\xmllite.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049 C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\apds.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\apircl.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\apss.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CbsCore.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CbsMsg.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cmiadapter.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cmitrust.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\cmiv2.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\CntrtextInstaller.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\dpx.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\DrUpdate.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\drvstore.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\esscli.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\fastprox.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\GlobalInstallOrder.xml C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\helpcins.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\locdrv.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\mofd.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\mofinstall.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\msdelta.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\mspatcha.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\OEMHelpIns.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\PkgMgr.exe C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\poqexec.exe C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\repdrvfs.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\smiengine.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\smipi.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\SvcIni.exe C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wbemcomn.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wbemcore.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wbemprox.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\WcmTypes.xsd C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wcp.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wdscore.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wmicmiplugin.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wmiutils.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\wrpint.dll C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\x86_installed C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049\xmllite.dll C:\Windows\winsxs\Catalogs\ba47519f54b38889385eefca5ab020c0ac61c1b841622d3de94b2a3a43bcb250.cat C:\Windows\winsxs\FileMaps\$$_servicing_version_6.1.7601.17592_a11607b30a47f76f.cdf-ms C:\Windows\winsxs\Manifests\amd64_41132c9135820a69ab9fcde658ad1324_31bf3856ad364e35_6.1.7601.17592_none_66b394c89e0fceda.manifest C:\Windows\winsxs\Manifests\amd64_fc1bde87f5bc34c852e947acaa841765_31bf3856ad364e35_6.1.7601.17592_none_4d581c651c62820b.manifest C:\Windows\winsxs\Manifests\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f.manifest C:\Windows\winsxs\Manifests\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_0b0e4b4025cf4049.manifest - modified files C:\Windows\servicing\Sessions\Sessions.back.xml C:\Windows\servicing\Sessions\Sessions.xml C:\Windows\System32\poqexec.exe C:\Windows\System32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb C:\Windows\SysWOW64\poqexec.exe C:\Windows\winsxs\FileMaps\$$.cdf-ms C:\Windows\winsxs\FileMaps\$$_servicing_fc2045b9046cc796.cdf-ms C:\Windows\winsxs\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms C:\Windows\winsxs\FileMaps\$$_syswow64_21ffbdd2a2dd92e0.cdf-ms C:\Windows\winsxs\FileMaps\_0000000000000000.cdf-ms C:\Windows\winsxs\ManifestCache\e4e8be02b8fae2a7_blobs.bin - deleted files C:\Windows\servicing\Version\6.1.7600.16385 C:\Windows\servicing\Version\6.1.7600.16385\amd64_installed C:\Windows\servicing\Version\6.1.7600.16385\x86_installed C:\Windows\winsxs\FileMaps\$$_servicing_version_6.1.7600.16385_9f2f8c770d21b01b.cdf-ms

It looks like that either Microsoft updated the article or i didn't read it properly the first time but Ms is providing a workaround to repair the install. Anyway i'll try tracing the changes made by the update.

Here is what i'll try: 1) install another windows 2008 R2 somewhere else (a VM would be my first choice) and disable UAC (as it might block installrite) 2) install installrite (as it should be the easiest way) and start it to take the "picture" before applying the MS Patch. 3) install the patch following installrite directions. 4) after installation (and perhaps reboot if needed), installrite will compare what was modified and will tell you which files/reg entries were modified. 5) filter the registry entries and system files found. 6) copy the files and create the reg entries you decided after filtering. 7) boot with a winpe or a windows 2008R2 install CD (then select repair to get the command prompt). 8) copy the files and import reg entries (remember to load the offline hives) from step 6. 9) reboot and see if it's fixed. 10) use another tool to replace installrite if installrite failed to get the files/reg entries added/modified/removed. Perhaps, if i find enough time, i'll try playing with this but i don't know if it will be soon.

Indeed, pretty stupid from MS not offering a proper way (the only way seems to restore) but perhaps the usual tools procmon, regshot or installrite can help you to find (monitoring the patch installation on another windows 2008 install) how to apply the fix offline and repair your install.

The win7 driver might work for XP but TRIM won't work (as it has to be supported by the OS). As the OCZ revodrive is bootable, it should be emulated by bios and so i think it might work without specific driver (as any other ide/sata drive) but it might work like a raid/scsi/sas controller and then drivers may be required. And if you find a clear answer, i will be pretty interested. If i had one, i would be glad to test

Hstart should help you.

To find what is modified when upgrading, you could try installing in a VM windows 2000 like your install then install the first "super" version then run installrite to monitor the install of the lastest version. Then installrite should tell you exactly what was modified and you should be able to fix your actual windows 2000 install. As a side note, i also used "super" a few years ago but as it wasn't stable and a real open source project; i replaced "super" with avidemux and i find it a lot better and more tunable.

Maybe you could tweak your lsi controller to get better performance but you won't get great speed with this very basic controller (even using a raid 0): You could try to enable or disable the disk read/write cache (some raid controller disable it and this one disable it usually), you could create a tweaked raid volume depending on the data stored (small files need usually a small strip size).

You're confusing things: forward dns record (a "A record" stored in the forward dns zone and resolving to a numerical ip) and reverse dns record (a "PTR record" stored in the reverse dns zone and resolving to a "A record") and in your case there might be (or not as you didn't use nslookup) only a PTR record in the reverse dns zone but nothing in the forward dns zone. Also checking dns records should be done with nslookup and not ping.

The root cause is probably a path longer than 255 (or so ) characters. To resolve this problem, you need to either reduce the path before the problematic folder (by renaming upper folder to one character) or to share the deepest level where the security tab appear and then connect the newly created share and try to set rights there (the security tab should appear now).

I totally agree with you i never heard a good feed back about Biostar make (but perhaps it isn't that bad) but the motherboard doesn't seem to support than 4GB of memory !!!!! How a make can do such a useless product (i could understand only 4GB for a laptop/industrial motherboard but never for a desktop computer) ? I wouldn't focus on getting an ich10 but more on getting at least an ich8 if you want to keep your cpu and RAM. Anyway as i see it, and if it was for me, i wouldn't try too much to repair or buy old parts in this particular case. I would just have one more reason to buy an ivy bridge (when they are out but it should very soon) and sell all unneeded parts.

Yes either sell old hardware and replace it by something new or try to find a motherboard with P35 chipset like this one as this will give you an ich9 and don't take you back in time to much.

I would avoid the G41 chipset as it include onboard video and you shouldn't need it with the ATI HD5670. But of course most big shops doesn't sell most of lga775 socket motherboard with another chipset (like an ich8 or an ich9).

But windirstat already do this for free.

This should do it (sed.exe is needed and is a port of gnu sed from the unix tools) : type file| sed ":a;N;$!ba;s/=\\\n\ /=/g"

This MS KB might help at least the last part as you moved the VM so perhaps the ntfs rights need to be fixed.

How the first one installed on your computer ?

Login server and dns are the Active directory domain controller role. To my knowledge, you should be able to add and perhaps promote the windows 2008 server as another controller but i wouldn't do it as it is highly recommended to have all domain controller running the same OS.

If the network printer is connected to a print server, you need to setup on the print server another printer queue with the chosen tray set as default. If the network printer isn't connected to a printer server, you need to setup on your computer another printer queue with the chosen tray set as default.

I use robocopy for this kind of tasks.

You could try to setup something like this: virtualize the current windows 7, then install on the physical computer an hypervisor (like a vmware esxi ). This way when the power is back online the hypervisor will restart and you should be able to remote control the VM and enter the truecrypt passphrase at boot.

If you downloaded the file AMD_AHCIRAID_V311540127_V120125_XPVistaWin7.zip, you will find a folder driver then winxp and inside you should find 2 folders containing the actual drivers x64 and x86. Extract all files contained in the winxp folder (and subfolders) to your floppy and be sure it contains at the root a file named txtsetup.oem and two folders x86 and x64 (containing 3 files each ). This floppy should work.

I can confirm that my monitor is reporting its serial in hwinfo32 report.