Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About suttle

  1. Hi guys, I've been using a nLited WinXPPro for almost a year now and it has been working great. Now I wanted to do it again so I could get a nice slimmed down and updated version of XP with all hotfixes integrated along with WMP11 and IE7. However, for some reason my new version of XP does not like the printer. As soon as I turn it on I get a shutdown dialog (XP shutting down in 60 seconds) saying that services.exe referenced memory at 0x00000000. The printer worked fine in my previous version so something is obviously wrong with my new XP. The question is does anyone know what the problem could be, have I removed something that I shouldn't? These are the steps I've done to create my XP image. 1. Use RVMIntegrator to integrate RyanVM Update pack 2.1.7 (there seems to be a problem using nLite for this as it doesn't seem to be able to integrate kb924667 properly as the hotfix shows up in WU), RVMAddons.1.8.1, RVMAddonsDX9.1.1, RVMAddonsWGA.1.5. and Kels.Royal.Remixed.Addon.1.45. 2. Integrate IE7 with nLite. 3. Restarting nLite and integrating IE7-KB929969 and IE7-KB928090. 4. Restarting nLite and using the attached preset WinXPLeanAndMeanNlite. I installed XP on my machine and used it for a couple days with no problems (though I had to install the nVidia drivers again even though they were supposed to have been integrated). I then realized that I hadn't installed the printer so I installed the drivers for the HP Photosmart 3110 All-In-One and then afterwards when I turned the printer on I get the aforementioned forced shutdown dialog. Any ideas? WinXPLeanAndMeanNLite.INI
  2. Well your reply about conflicting Administrator autologin and oobe creation seemed like it could be an explanation, but unfortunatately it's not that. I removed AutoLogon and my GuiUnattended now looks like [GuiUnattended] DetachedProgram="RunFirst.cmd" EncryptedAdminPassword = No AdminPassword = "secret" TimeZone = 255 OEMSkipRegional = 1 OemSkipWelcome = 1 My oobeinfo.ini gets copied to C:\Windows\system32\oobe\oobeinfo.ini, but no user is created and I have to enter the Admin password go get RunOnceEx to start.
  3. They are talking about getting the license directly from Microsoft. In your case it's Eagle Computer that before had to order the OEM versions in batches of 3 or more, but if you now register as a "computer builder" you can order one single license from Microsoft.
  4. Well I don't get it. I have [unattended] UnattendMode = DefaultHide (I've also used FullUnattended) UnattendSwitch = yes OemPreinstall = Yes ... Still no user "Martin" created. And if I look in the Documents and Settings folder it looks weird. These are the folders that show up. Administrator Administrator.RAPTOR (the computer's name is RAPTOR) All Users All Users.WINDOWS Default User Default User.WINDOWS LocalService LocalService.NT AUTHORITY NetworkService NetworkService.NT AUTHORITY On my manually installed windows it looks like All Users Default User LocalService Martin NetorkService The oobeinfo.ini file gets copied to C:\WINDOWS\system32\oobe\oobeinfo.ini and the content is [userInfo] Identity000="Martin" [Options] (this line was added by windows) IntroOnly=1 (this line was added by windows) This is getting annoying.
  5. This unattended process seems to be a very delicate one. A thing that is working at one point stops working the next. At one point I managed to create a user using this oobeinfo.ini (in the $OEM$\$$\system32\oobe directory). [UserInfo] Identity000="Martin" Now it seems like I've changed something that prevents user creation from happening since I just end up with the Administrator user. In my winnt.sif I have the following [GuiUnattended] EncryptedAdminPassword = No AdminPassword = "secret" TimeZone = 255 OEMSkipRegional = 1 OemSkipWelcome = 1 AutoLogon = Yes AutoLogonCount = 1 I'm using autologin here so the RunOnceEx will kick off and after that is done and the PC reboots I expect to end up on the login screen where there should be a user Martin, but there's just the Administrator. I thought I had it down pat this time, but noooo Do I have to use the net user command instead?
  6. I told you it was something obvious Thanks for that. It would have taken me at least a couple of days to figure that out. I even had a echo %CDROM% >> D:\cdrom.txt just to see that it was correct, but ofcourse I didn't notice the blank space. I guess I have to figure out the display thingie now. Integrating catalyst 5.11 with nLite doesn't seem to do anything. It may be working and the problem is that I can't validate it via VMWare.
  7. I'm trying to install a few programs directly from the CD without doing the $OEM$\$1\ trick And this is what my RunOnceEx.cmd looks like cmdow @ /HID @ECHO OFF FOR %%i IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\WIN51IP.SP2 SET CDROM=%%i: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\001 /VE /D "Windows Messenger 5.1" /f REG ADD %KEY%\001 /V 1 /D "%CDROM%\Software\messenger\messenger5.1.msi /qn" /f REG ADD %KEY%\015 /VE /D ".NET Framework 2.0" /f REG ADD %KEY%\015 /V 1 /D "%CDROM%\Software\netfx\dotnet2.exe" /f REG ADD %KEY%\085 /VE /D "Cleaning Up and Rebooting" /f REG ADD %KEY%\085 /V 1 /D "%CDROM%\Software\cleanup.cmd" /f EXIT Now, if I use this I'll just end up with 3 explorer windows listing the contents of my CDROM install disk. I've more or less copied this directly from "Running RunOnceEx from CD" so I don't understand why it's not working. Hopefully it's something obvious that you guys can point out straight away. My CD looks like $OEM$ DIR I386 DIR Software DIR boot.bin File WIN51 File WIN51IP File WIN51IP.SP2 File I can get it to work if I put my Software folder under $OEM$\$1 and change %CDROM$ to %systemdrive%, but I want to do it from the CD. And as a sidequestion In my Winnt.sif I have [Display] BitsPerPel=32 Xresolution=1024 YResolution=768 Vrefresh=85 However I still end up with 800x600 and I have to change it myself to 1024x768 Ideas?
  • Create New...