spacesurfer Posted August 29, 2006 Posted August 29, 2006 If anyone has any insight, I ran into a weird problem when I reinstalled Windows XP. Here's what I did:I used RyanVM pack August update to make my installation CD.During the first installation, I wiped out my HDD using XP setup and created my NTFS partition C:\ for Windows. During the GUI portion, I got an error dialog box saying something wrong or missing file G:\runsetup.dll. I pressed OK and it installed.After installation and during first logon, I got device manager looking for battery drive for a Dell Latitude laptop. I never had problem with RyanVM pack June version. I started with July and August. Anyway, I had to disable the battery (there are three showing up in device manager).It was an unattended installation and I screwed up so I decided to reinstall. I had already created D:\ partition (NTFS primary) for documents, E:\ (NTFS primary) for programs, and F:\ (FAT32) for Win PE.When I started reinstallation, I deleted C:\, then re-created. When I did this, it showed unpartitioned space of 8 mb before the C:\ partition. I didn't know what that was and didn't like it but I couldn't get rid of it. So I let installation continue.When I finished, I noticed that ntldr and boot.ini was not in my C:\ partition but my D:\ partition. Obviously, reason was C:\ was an NTFS extended partition. D:\ was my first primary NTFS partition. Why did XP setup create an NTFS extended partition?????????? That's weird.This obvious is not a good setup since if I format d:\, then I loose my ntldr and boot.ini.Anyway, if anyone knows why:1) with RyanVM pack july and august, I get that runsetup.dll error and battery error.2) Why XP setup makes my partition extended when I choose to reinstall when D:\ and E:\ are already present.Thanks.
spacesurfer Posted September 5, 2006 Author Posted September 5, 2006 Since nobody's commented...I reinstalled like 20 times, and narrowed the runsetup.dll error during GUI setup to a device driver (I don't exactly know which one, but I was using Pyron's method to detect drivers during install).The battery problem still persists. I tried April, June, and August RyanVM packs and they all give me no battery drivers. So I have a laptop that I can't put into standby. It remains on all the time.My only option was to use a ghost image I had created that had those drivers.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now