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 Jasonthejoker

  1. It was indeed the location of the oem folder. id*** I am! RIS now working excellently for several models. Thanks for your help guys. Jason
  2. Think I may have another idea. Just read a post on MS site that says the $oem$ folder should be at the same leel as the i386 folder. Mines in the i386 folder. Could this be the problem? I suspect it is and have moved the folder and restarted the service. Can't try the install now though, it's half term and the server is at work!
  3. Are there any sensible steps we can take to make our RIS installetions faster? I'm guess the windows installation stage can't be optimised as it's the same as it would be for a disc based install. Are there sensible steps I could take to increase the speed of the first stage and is it wise/advisable to do so? Thanks Jason
  4. Is there a list of possible commands in an RIS answer file? I can find lots of examples, but wondered if microsoft or someone else had a definitive list of the commands/lines and syntax. Thanks Jason
  5. Thanks. Unattended file below. I've done another machine which is working fine, but not adding to the domain. Unattended file created using windows tools and applied to existing image (Which uses second answer file) ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="1" UnattendedInstall="Yes" floppyless="1" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" OriTyp="4" LocalSourceOnCD=1 [SetupData] OsLoadOptions="/noguiboot /fastdetect" SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No TargetPath=\WINDOWS FileSystem=LeaveAlone NtUpgrade=No OverwriteOemFilesOnUpgrade=No [GuiUnattended] AdminPassword=[Encrypted password] EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=85 OemSkipWelcome=1 [UserData] ProductKey=[Product key here] FullName="User" OrgName="Lea Valley High School" ComputerName=%MACHINENAME% [Display] BitsPerPel=32 [RegionalSettings] LanguageGroup=1 Language=00000809 [SetupMgr] DistFolder=C:\windist DistShare=windist [Identification] JoinDomain=%MACHINEDOMAIN% DoOldStyleDomainJoin=Yes [Networking] InstallDefaultComponents=Yes ProcessPageSections=Yes [RemoteInstall] Repartition=Yes UseWholeDisk = Yes [OSChooser] Description="Windows XP Pro SP3 Automated" Help="This will install Windows XP Pro SP3 without user intervention." LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType=Flat Original answer file:
  6. Could try a manual install, but it's a netbook so I'd need to grab an external drive from somewhere. In the meantime I'm trying a different version of the SATA drivers. Sopme questions: Should OEM drivers be put in the directories (i386 & $oem$\1$\drivers\*) with standard "*.sys;*.inf" extentions or should I change them to compressed style "*.sy_;*.in_" format? I've prepared an answer file using the windows tool and applied this to do an unattended install of an existing image. Does this new file reference the original SIF in addition to the answer file? Using the unattended install the screen skips the format screen almost immediately when you see it. The standard one delays here slightly. I had assumed this wasn't a problem, but being that it's a HDD error I wonder - Could this be a problem? In addition I've noticed that that the UseWholeDisk line is missing from the unattended SIF file, although it exists in the standard one. Could this be a problem? Hoping that I'm moving closer to a solution!
  7. No IDE Compatibilty mode in BIOS. I've added the SATA to the RIS image as per instructions on the HP website here. Notice the convenient method of doing GIFs for the text portion, hence no copy paste! My TXTSetup.SIF as below: [SourceDisksFiles] {Some entries} iastor.sys = 1,,,,,,4_,4,1,,,1,4 iaAHCI.cat = 1,,,,,,,20,0,0 iaAHCI.inf = 1,,,,,,,20,0,0 iaSTOR.cat = 1,,,,,,,20,0,0 iaSTOR.inf = 1,,,,,,,20,0,0 {More Entries} [HardwareIdsDatabase] {Some Entries} PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0104 = "iaStor" PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor" PCI\VEN_8086&DEV_25B0&CC_0104 = "iaStor" [SCSI.Load] {Some entries} iaStor = iaStor.sys,4 [SCSI] {Some entries} iaStor = "Intel(R) 82801 SATA RAID/AHCI Controller (ICH5,6,7)" My ristnrd.sif file contains: [Unattended] OemPreinstall = Yes OemPnpDriversPath = \Drivers\SATA OemPnpDriversPath = \Drivers\LAN OemPnpDriversPath = \Drivers\Display OemPnpDriversPath = \Drivers\Display\Graphics OemPnpDriversPath = \Drivers\WEBCAM\XP OemPnpDriversPath = \Drivers\CardReader\DriverBin_32bit OemPnpDriversPath = \Drivers\Chipset\All driversigningpolicy = ignore Contents of SATA driver folder as below: Thanks
  8. UPDATE! I feel a bit silly now. Just done an F8 and chose disable automatic reboot and get a complete BSOD screen. The error code is: *** STOP: 0x0000007b (... Will investigate this, but any help you guys can give would be very much appreciated. Jason
  9. If I do safe mode when rebooting the final entry is as per the picture below. It's Mup.sys. Short delay on this screen then the above BSOD which stays for asecond or two. In order to get to this stage I had to add NIC driver and also add SATA driver. Thanks in advance for your help guys.
  10. I had already done that. Picture below. I'm 99% certain that there is no more than this, it's not just that it's missed on this frame.
  11. The blue screen appears on first reboot after installation, so it never makes it into windows. Has anybody experienced this before? Alternatively has anyone successfully done Compaq netbooks via RIS? I'm fairly sure the blue screen doesn't show a complete message before the system powers off and back on.
  12. Hi everybody, I;ve used RIS in a previous job and we're just starting to use it here for our installations. I prefer it to Ghost, which is our current method. I have a batch of 10 Compaq Mini 110c Netbooks, which will be soon be followed by an additional 150 units! Having spent some time working on this we have the following: Windows XP Pro SP3 installation from fresh download from Microsoft Licensing site RIS install with modifications to include NIC and SATA drivers Install completes and we get BSOD on reboot after windows portion We've made progress from yesterday, when we couldn't get past initial RIS screens. My question now is what can be causing the BSOD after windows reboot. The message flashes for a fraction of a second and starts "A problem has been detected..." The screen only goers as far as "Technical informa." at which point screen goes blank. I can;t really get anything useful from this to try and work through the problem. I've included NIC, SATA and Display drivers in OemInstallPaths. My instinct is that it's a display related problem. I get the same issue if I make it full unattended or if I don't. If I do Safe Mode with Command Prompt on subesequent reboots the last driver that loads is ...\System32\Drivers\Mup.sys. Any thoughts?
  • Create New...