Mordac85

What version (Home or Pro) and SP are you working with?

Why not just let them work on the network files (directly through a persistent drive mapping if they can't handle a UNC)? Also, if a username is required wouldn't they also need to provide a password? If so, is this system part of a domain or a workgroup?

Good point that I forgot to mention. RDP logs out the end user and locks the remote system so all the end user sees is a locked WS screen. I use Netmeeting when I need to do something interactive.

Don't forget boot.ini is also read-only. You'll need to clear that before you can save your changes. I'd also recommend making a backup copy in case you get into trouble so you can restore the default.

You need to add a line in your AUTOEXEC to call Ghost. I boot to the network, map a drive to my image share, wipe my target drive, clear the MBR and restore whatever image I want. To automate the restore you could use something like: <path>\gdisk.exe 1 /del /all /sure <path>\gdisk.exe 1 /mbr <path>\ghost.exe -clone,mode=load,SRC=bakimg.gho,DST=1:1 -sure -rb The switches are all in the Ghost manual. If your image spans to multiple files (*.ghs files) you only have to call the *.gho file in the SRC switch and Ghost will grab them (from the same directory) as needed.

Thanks for that bit o' trivia! I started using Ghost about a year after Norton acquired it but couldn't remember who actually created it. Dropping the image file to your data drive is an excellent idea too! Image restores fly when it's just disk to disk. Whether it's Ghost or Acronis or something else I think HyperHacker is looking in the right direction.

M$, while shady in some areas, is not trying to "spy" on you. They use intermediary servers to route your help request and help establish the connection. It's not a simple point to point connection. That's why I prefer to initiate the RDP connection to a known system or IP, or use Netmeeting.

Since the majority of the imaging market is Symantec's (Ghost and DriveImage) they are the favored, and best understood. I too have been using Ghost since the early days @Norton and cannot sing it's praises enough. When it comes down to changing HW, I'd go ahead and plan on a fresh build anyway and then Ghost the new build. A couple of tips for you. First, make an unattended install so a fresh build isn't that painful. The MSFN Guide is very helpful! Second, if you move your profile to the data partition, you won't loose your settings and such either.

IMHO it's easier to just use RDP (Start\Accessories\Communications\Remote Desktop Connection) and plug in the remote system name or IP (depending on what your network layout is like and has to be enabled on the far end). There are a lot of what ifs involved in either situation, but well worth it. If the remote is behind a firewall or some such where you cannot connect w/RDP, you can always fall back to using desktop sharing in Netmeeting.

Since IE is running under the user context, if the user has rights to modify it, then it is possible.

WinPE is a pre-installation environment, a pared down Windows environment, that can be very helpful for working on an NTFS drive having problems. MSFN has a whole forum for it here. Given your response, I'd stick w/just rebuilding the system.

The Linux distro is a personal preference. I would recommend reviewing one of the various DualBoot HOWTOs on the web, a good place to start is the Linux Documentation Project. Another good refs is Ed's Software Guide on Linux I've had much better luck building the system linux w/room for my Windows install. If I remember correctly you install linux w/free disk space for your windows install starting w/in the first 8.5GB. Then install Windows on the free space. When I'm done w/the base install I add a line in grub for Windows and edit the boot.ini. If it's working, I continue loading the rest of my apps and tweaks. Last time I did this it only took a few hours to get both OS's up and running. The HOWTOs out there are very helpful.

I'm assuming they are different domains then? I believe there are a few 3rd party pkgs that will do it, but it'll cost. How about building a 'backup' server in the new domain using any old 32 bit system you have and make it a DC. It may be slow as puke, but you'll only need it for a short time. Then run ADMT to the new DC. You may need to isolate, or shutdown, the 64 bit DC to eliminate any interference, but that should do the trick. Now, for my 2¢. I would drop the idea of migrating accounts. Looking back at our migration of 8500+ accounts we would've been better off creating them from scratch and scripting the permission changes. Start it clean, don't carry over your acquired problems. The users knew it was coming and were very accomodating of the changes so take advantage of it.

I've never had an issue w/Ghost not creating a bootable image. That is as long as you're doing a dump and not a copy or partition dump, which does not grab the MBR. I've been using Ghost for years w/o issue so I'm kinda stumped as to why you'd be in a situation like this. Could you post the command line used that gives you grief?

Did you try a System Restore from prior to your 'help'? I'd also highly recommend tracking down those restore CD's cuz you'll most likely need them, and the license key, for when you have to rebuild the system. When, not if, since a laptop is like an Indy race car. You'll be in the pits sometime, it's just a matter of when. Also, it's advisable to uninstall applications, not just delete the program directories.

Sorry, I thought you could get into it thru Safe mode. You would have to be able to find and fix the problem outside of the OS from a WinPE CD, a linux boot disk or by slaving it into another system. Given the lack of info to go on, it's gonna be a tough job. Personally, for a situation like this, I would rebuild. You can't get access to the system to do much about the problem and I tend to cut my losses when faced w/the law of diminishing returns.

When you get the BSOD it will have some other information like so: The other pieces of information refer to exactly what is involved: Item 1 - The address that was referenced improperly Item 2 - IRQL that attempted to access the memory Item 3 - Type of access (0 is a read, 1 is a write) Item 4 - Address of the instruction that referenced memory in item 1 Now the IRQL_NOT_LESS_OR_EQUAL is sooooo ambiguous that it could be RAM, hardware, a driver, your BIOS, just about anything. However, since you're also getting the Page Fault error I'd start looking at a bad, or buggy, driver. The filename(s) listed on the BSOD should get you pointed in the right direction.

OK, I didn't know there was a diff in those shrtcuts Symlinks are so much easier... And since I'm new to the boards I don't want to sound offensive.

I'm sure your solution will help a lot of others too (maybe even myself).

It will probably die just when you start copying your data out. Drives seem to be uncanny at picking the absolute worst time to give up the ghost.

Not quite. We were talking about a hack on the file that shows the text above the oemlogo (Manufactured and supported by:), not the oemlogo itself.

If you're using nLite and select 'Create a bootable ISO' you shouldn't have an issue as long as you used the original source files from the XP CD. To me it sounds as if the CD isn't bootable or you have the HDD before the CD in the boot order. Check your BIOS first for the obvious boot order mistake, then check your CD for WIN51 in the root. If it ain't there, I doubt if the CD is even bootable.

Read and all will be revealed! And also more detail: And the pièces de résistance: Looks like a disk error. Considering the strange noises, your drive is most likely on it's death bed. If it sounds like clicking noises or scratches, grab your data while you still can and order a replacement.

I'd have to also take exception to the article's statement that 99+% of systems still use the old LM hash method. Maybe 99% of the SOHO's and home users are but, IMHO, any company w/an IT staff worth thier salt have already shifted to NTLMv2. And if MS truly wants to even appear as if they are taking a more secure stance, they'll enable not storing the LM hash by default.

Not to sound harsh, but it is the answer he asked for. IMHO, it's much better to find out how to toggle the switch, and therefore how the system works, than to throw a shortcut in as a workaround.