ben
windows xp BSOD Stop 0x0000007E
so after an architecture change of a client’s server’s pc during a disaster recovery middle of business day, i was forced to learn a lot about migrating windows xp install to and from intel and amd architectures.
i found the repair to be sufficient moving from amd to intel, but left me with a BSOD when going from intel to amd.
well like most microsoft problems, this error has a bajillion reasons as to why and finding pertinent information was difficult. i finally stumbled across this microsoft kb artice (http://support.microsoft.com/kb/953356) which instructed that when the repair cd was created via an image that was intel-based, it needs to have a registry key disabled in order to boot on amd.
fortunately, since even safe mode is not accessible during a half-complete repair, the kb article even documented how to disable the feature via the recovery console of an install cd
i cite the kb article here:
To work around this issue, run the recovery console by using the Windows XP CD. Then, select the recovery option. To run the Recovery Console from the Windows XP startup disk or from the Windows XP CD, follow these steps:
- Insert the Windows XP startup disk in the floppy disk drive. Or, insert the Windows XP CD in the CD drive. Then, restart the computer.
Note If you are prompted, click to select any options that are required to start the computer from the CD drive.
- When the “Welcome to Setup” screen appears, press R to start the Recovery Console.
- If you have a dual-boot computer or a multiple-boot computer, select the installation that you want to access from the Recovery Console.
- When you are prompted, type the administrator password.
Note Press ENTER if the administrator password is blank.
- At the Recovery Console command prompt, type the following command, and then press ENTER:
disable intelppm
- To exit the Recovery Console and to restart the computer, type exit at the Recovery Console command prompt, and then press ENTER.
remove stale locks vmware server 2
so my virtual machine server went down in my office the other day, and the auto startup for a specific machine failed because there was a lock file present from before the power failure (time to replace my ups)
it was easy enough to fix by removing the folder located at:
/var/lib/vmware/Virtual\ Machines/{vm-name}/{vm-disk-file-name}.vmdk.lock/
for me the command was:
# rm -vfr /var/lib/vmware/Virtual\ Machines/nataile/natalie-hardDisk1.vmdk.lock/
reparse and remount fstab
after adding a usb drive to fstab i reloaded it and remounted when needed using the following command:
# mount – a -o remount
funny stuff!
unpack multiple files at once using xargs
how to upack all tarball gunzips .tar.gz in a given directory at a time
ls *.tar.gz | xargs -t -I {} tar -zxvf {}
*note: after the -t it is a -I as in -(capital)i
substitute your flavors at -zxvf and adjust file list at the ls command before the pipe
compiling from source against 2.6.33
i screwed up my slackware install on my laptop, did a reinstall, realized i installed 32-bit and decided to roll with it. everything i have gone to install out of the official tree has needed some patching due to the new kernel.
apparently the new kernel (2.6.33) no longer generates a file named /usr/src/`uname -r`/linux/autoconf.h and instead generates one named /usr/src/`uname -r`/generated/autoconf.h –> what this means to compiling from source is that all references to the linux/autoconf.h must be redirected to generated/autoconf.h
trust me that this is a major headache that isn’t very well documented yet
