I really wish hardware vendors would provide an application that could check all the provided software for updates and then download & optionally install them. It didn’t apply directly to her system, but the version was pretty close.
A bit more searching and I found an update to the software “eRecovery” software. I checked the Gateway site to see if the software had been updated … but couldn’t find anything specific to the system we had purchased.
I tried to burn the Applications & Drivers DVD, but kept getting an error 205 from the Gateway Recovery Manager, no mater what DVD burner I used (the built in device or my external USB DVD-RW).
It wanted 4 DVD’s (or a box full of CD’s) … which I had. The systems “Gateway Recovery Manager” software kept bugging Ginny about creating recovery disks (since the system didn’t come with any OS media). Realizing that CompUSA would give us a hard time about returning the system, Ginny tried Second Life out and declared it to be adequate. It was then we realized that the system’s video wasn’t up to Second Life’s standards. I then ran One Key Recovery and it said something like unable to. I used the PTEDIT32.exe utility from the link provided and managed to hide the SYSTEM partition. Hi yigit, I did what you had instructed, backed up my data and created recovery disk using default factory settings. Most of her other computers were hand-me-downs (from me). Re: Partition and drive letter assignment. FWIW: This is Ginny’s first new computer in quite a while. The only problem was that it had on-board Intel video and no DVI output (although it does have HDMI output). We chose a Gateway SX2800-01 system (Core 2 Quad, 4gb RAM, 640gb SATA disk, 64bit Vista Home). So we went over to CompUSA (formerly Tiger Direct) and looked at the small form factor desktop systems. Well, her laptop (Dell Inspiron 8600) is almost out of warranty … and she’s not going to be getting my Dell Latitude D630 (due to the Latitude E6400 being returned), so I figured it wouldn’t be a bad idea to get her a new computer. It wouldn’t book up, just gave one long beep, waited a few seconds, gave another long beep, over and over. Before the process is finished, don't close the command line! When the process is finished, try restarting the software that you are experiencing the errors in after closing the command line.A few days ago Ginny’s desktop machine (a home built system cobbled together from various parts I had on hand) finally gave up it’s ghost. The process can take some time depending on your computer and the condition of the errors in the system. 2 insert your drive key with PTEdit32.exe on it during booting (or before) 3 navigate to your drive key 4 run PTEdit32.exe 5 PTEdit32 will show 3 drives one will be considerably smaller than the other two and will have a value of 12 or 27 or such change this value to 07 6 Save and close PTEdit and reboot into your Vista operating system.Rename 'CMD.EXE' in the Utilities folder to 'PTEDIT32.EXE'. Now copy 'CMD.EXE' from I386System32 to the Utilities folder. Rename it to something like so you can put it back later if you wish. Now choose one of the utilities you can live without. sfc /scannow Step 2:Getting rid of Windows Dll errors by running the sfc /scannow command Navigate to the I386ShellUtilities folder. Type the command below into the Command Line page that comes up and run it by pressing Enter on your keyboard.Step 1:Running the Command Prompt as administrator Right-click the " Command Prompt" search result that comes up and click the Run as administrator" option.We also typed in " cmd" to bring up the Command Prompt. This process will enable you to run a search through the Start Menu. Open the Start Menu and before clicking anywhere, type " cmd" on your keyboard.If you are using Windows 8.1, Windows 8, Windows 7, Windows Vista or Windows XP, you can use the same method to run the Command Prompt as administrator. NOTE! We ran the Command Prompt using Windows 10. Did a NTFS format, push the Novo key and restored the factory Vista. On the Boot record, change Hidden Sectors too. and the Sectors field to (PartitionLength / BytesPerSector). In order to do this, all you have to do is follow the steps below. Using PTEDIT32 I changed the field 'Sectors Before' to reflect the field 'Hidden Sectors' on the wsi. In order to complete this step, you must run the Command Prompt as administrator.
How to Fix PTHSP.DAT manually Method 1: Solving the PTHSP.DAT Error Using the Windows System File Checker