Jump to content

Wolluf

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

About Wolluf

Wolluf's Achievements

0

Reputation

  1. I've found the culprit - KB943460, released last month - if anybody's interested!
  2. Rather odd then, as XP installations with all updates (from non-slipstreamed start) installed don't have the same issue. Also, it didn't happen with previous versions of nlite (though other things did of course, like the sfc issue). If it is one of the patches, does anyone know which one?
  3. Hi, Using nlite 1.4 final just slipstreaming hotfixes (most since SP2) - not doing anything else. Installed with resulting iso file (just a virtual machine to test) and the option to show/not show internet explorer on the desktop in display properties (desktop tab) is missing. It is available from tweakui. Note. If I just slipstream ie7 & WMP11 to SP2 base (ie, no hotfixes), icon option is still available. I really don't want to try all the hotfixes one at a time! Not a major issue, perhaps, but a little worrying, inasmuch as if this option is missing, what else may be affected which I haven't seen immediately - and I did choose to not modify the install. Any ideas? Thanks
  4. I have same issue - and not supplying any unattended settings. Also, oddly didn't previously have it with 1.4 beta. Recent production. Base is xp with SP2. Added ie7 & wmp11 with SFC turned off. Then added patches (currently to end Aug). This was previously ok with patches to June - but now get Kabul setting too (this is after setting GMT/UK during the setup process). Supplying unattended parameters makes no difference (and it still prompts for time zone! - and it still sets Kabul after GMT is selected!). Also causes install to jump the initial install/repair dialogue I do think nlite is excellent - but it does throw up these issues too frequently - which suggests changes to settings which are nothing to do with the user interface
  5. Nuhi - posted this in an older thread - the nlite under vista problem - don't know if the event log entry any use:- I'm getting this problem too. When trying to insert a patch - select one from where they're stored and get message nlite has stopped working. Event log shows:- Faulting application nLite.exe, version 1.3.9.0, time stamp 0x466fbce4, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id 0x670, application start time 0x01c7f6b1e78d2c38. Running nlite 1.4 beta on Vista Ultimate. Have tried running nlite as Administrator too - same.
  6. I'm getting this problem too. When trying to insert a patch - select one from where they're stored and get message nlite has stopped working. Event log shows:- Faulting application nLite.exe, version 1.3.9.0, time stamp 0x466fbce4, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549bdc9, exception code 0xc0000374, fault offset 0x000af1c9, process id 0x670, application start time 0x01c7f6b1e78d2c38. Running nlite 1.4 beta on Vista Ultimate. Have tried running nlite as Administrator too - same.
  7. Hi, Have winlite install disk with SP2 and all critical patches since and ie7 integrated - nothing else - no tweaks etc. XP installs fine - but after installation, at some point (usually when installing drivers) get the 'critical system files have been replace by unrecognised versions' message. Cancelling message doesn't cause any problems - but wonder if anyone else has had this? It seems to have started since version 1.2 and ie7 integration. Main problem for me is I use winlite disk to effect repair reinstalls on my customer's machines (when necessary) - as it obviously saves reinstalling all the updates again - and if they see this message, its obviously worrying. It usually only happens once (so its already happened by time I return machine), but occasionally it happens several times. Anybody know why this is and how to fix if possible? Thanks
  8. Just like to add I get this too - starting with no service pack source for Pro, nothing done to it and using nlite to slipstream SP2 then all the criticals since then plus ie7 & wmp11. Install completes, but no prompt for username & lots of services not starting (like its been 'optimised' - except it hasn't)
  9. I may be being stupid (have only dabbled with unattended/slipstreaming, definitely not an expert) - having similar problems with SiS965 SATA/RAID controller on an Asus K8S-MX - but how does editing the registry hives enable the initial part of the install process to see the drive?
  10. Have set up a 64 bit test machine with a SATA drive and no floppy (well, no permanent floppy) drive. Trying to create 64 bit XP install disk (evaluation copy currently) with the SATA drivers included. The SATA/RAID controller is silicon integrated systems (SiS) 965 (on an Asus K8S-MX board). I've succesfully created a 32 bit install with the drivers added, but doing exactly the same, but using the 64 bit driver doesn't work (no hard drive detected). If I connect a floppy drive and use F6 and the drivers on the floppy, it works - so driver is obviously ok. I did have some problems with the 32 bit too (if nothing else, took me a while to realise the RAID drivers were all that was needed. Also following different instructions on the web - but final working set up just meant adding the driver to \i386 and putting a few sections at the end of txtsetup.sif - ie, didn't use $OEM$\$1 or winnt.sif. So I tried the same for 64 bit (except used \amd64 of course). Then tried using OEM stuff - all no good. So wonder if anybody here has any ideas? btw - the 'floppy' drivers have this file/folder structure (I mention it as its not flat, and might have some bearing - and they're available from http://www.sis.com/download/download_step1.php if anyone want to see what they look like:- Sisraid - text file Txtsetup.oem - text file RAID - folder - srv2003 - folder (not interested for 64 bit) - winxp_2k - folder (not interested for 64 bit) - WS03XP64 - folder - sisraid.cat - sisraid2.inf - sisraid2.pdb - sisraid2.sys (the 32 bit has a property.dll instead of a sisraid2.pdb - but I got it to work with just sisraid2.sys) Thanks for any help
×
×
  • Create New...