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 rustycaps

  1. I found the easiest way was to extract the files from the exe to a folder and integrate them along with the drivers during nLite config. It extracts a couple of mshda*.inf files (and prob others too), and seems to work a treat.
  2. Regional Settings

    I just saved the registry settings for this folder and added it to the regtweaks file - [HKEY_CURRENT_USER\Control Panel\International] - once it was setup how I wanted it.
  3. dotnetfx 2.0

    "e:\dotnetfx2.exe" /Q /C:"install.exe /Q" /f This is the line from the updated runonceex I used to get it to work, as I noticed the same thing when I'd originally run the installation. Yours looks the same except for the quotes in the wrong place. PS - I run my apps from another partition/drive, which is why I have a specific letter, but does the same thing.
  4. Quick question - not wanting to hijack this thread - but with the change administrator name in nLite, is that added as a reg edit/batch after, as I don't want it to affect the existing winnt.sif if it was to use that?
  5. Desktop Background Issue

    That's originally what I'd meant by adding it to winnt.sif, but I either forgot to mention the line, or didn't know it off hand, or thought you could find it on here or other guides somewhere.... With the other stuff I mentioned, the attended part was for the WinWall program install, which is part of a batch file run at the end of RunOnceEx, mostly made up off attended installs, but designed to save me manually running everything later. That reg code was just something extra as well, seeing as both were on the topic of desktop related. Sorry if all that other stuff was too much, but yeah, that code is all you need - of course you need to configure and save the theme first - and possibly stick it in the $oem$\$$ folder I think under system32 or so, then reference to that when it gets copied locally as %systemroot%\system32\name.theme. You'd need the bitmap in the same folder or on a fixed drive that will stay the same when you install, or it won't work, unless you edit the theme in Notepad to specify the location, e.g. %systemroot%\system32\name.bmp
  6. Desktop Background Issue

    I've found it easier just to use a theme referenced in winnt.sif, which has a flooded bliss background and the colour/layout of windows how I like it pre-configured. I also have a desktop changer program called WinWall installed after RunOnceEx in a batch file run at the end of it, which has a reg file run before installation which will load a different wallpaper after it's installed (the installation is attended, with an option to run WinWall, which changes the wallpaper to one from a pre-defined directory set via the reg file run previously). This reg entry is also useful if you use the Ctrl-Alt-Del logon screen. ;Set logon box background image [HKEY_USERS\.DEFAULT\Control Panel\Desktop] "Wallpaper"="file source using \\ between folders"
  7. Promise SATA/ATA card problem solved

    So, I guess I could try and see if the newer drivers work using the existing (working) settings from txtsetup.sif, and just update the drivers and the sy_ file in i386? I checked the (your) site with info on the pack, but I don't think there's much difference in dates between the drivers I got working now from the old pack ( and the ones listed there ( I think), as mine shows up dated 6/12/03, though new ones on the Promise site are only listed as dated 4/28/05. I just noticed on your listing that the card I've got is actually listed down further (on 2nd thoughts, ignore that, cos I just realised/noticed on the manual that I've got the older/original card anyway!). I'd originally gone and downloaded the drivers for the SATA II 150TX2 plus thinking that's what it was based only on the 150TX2 Plus part (that's why the CDs didn't work too obviously!), but this isn't the SATA II card - site only lists as SATA 150 TX2 Plus, and drives aren't SATA II anyway, so all is good in that respect. I just looked through the Promise site under the main products menu, when I should have gone into the full product drop down menu which I did just then, and saw the version I really wanted..... I just had a look at the file from your site, and compared it with the filenames I got working here, and it's the P/6 folder that has the ulsata.sys file which is the same date, etc as what I've got working now, so basically I did all that for nothing in the end it seems.... I think I'll just leave it as is now, as it's working - I can't even seem to find the right card on the Promise site - there's either a SATAII150 TX2 Plus, or a FastTrak SATA 150 TX2 Plus, but I've tried the SATA II drivers without success and I don't think the card had Fast Trak printed on it...... FFS!
  8. Promise SATA/ATA card problem solved

    I just looked at the readme file from in the extracted directory and it was a RyanVM product with a changelog date of 20.5.04 (or 5/20/04 for US people). I know that this post may not be so useful as such, but I was just saying thanks for that file being posting and me remembering about downloading it, so it did what it was supposed to do.
  9. I just bought a Promise SATA 150TX2 Plus controller card (the one with 2 SATA and 1 IDE channel/s) the other day, and I'd gone and Nlite'd a CD with what I thought were the newer drivers for the card. So time comes to install windows (change boot drive, etc around, which is why I was reinstalling), and it only detects the primary boot drive and the (at the time) unpartitioned RAID0 array, so I let it reinstall, then I went and d/l some of the other drivers on the site, and re Nliting to no avail (when I tried to install), and even the floppy drivers didn't work (had to copy via file server as this system has no floppy drive). I had nearly had enough when I remembered I'd downloaded a RAID drivers zip file or something of here, which had a whole heap of RAID/ATA chipset and controller card drivers and txtsetup.sif code with it. I checked it for the Promise 150 series, and thankfully it was there, so I copied the necessary code into txtsetup.sif and the drivers into their proper locations and then after everything else needed to create the CD, it worked!! Only thing was that the controller card was detected before the onboard SIL RAID0 array, which stuffed the drive lettering around (changed 2 sata drives around and fixed it), even though boot order was RAID0 then controller card drives, but it's all working fine otherwise thanks to GreenMachince I think it was where that file was sourced from ages ago when I got it.
  10. To slipsream nVidia drivers

    Before I started using nLite, I discovered the easiest way to have the latest nVidia drivers installed was by using the OEMPNPDriversPath method to specify where the new files were, but then to delete the default XP nvidia drivers (nv4_disp.in_ and 1/2 others I think), and it worked fine (I had a Leadtek card which used non-standard drivers - maybe normal nVidia drivers might have worked, but thought it best to use the Leadtek drivers).
  11. WINNT.SIF question

    I've kept a copy of the original winnt.sif that has worked for me in "non-nLite" mode, so when I did it through nLite, I just copied over a few little bits that it missed (think the lines Repartition = No and AutomaticUpdates = Yes, and the custom theme line), but if I did too much to it, it stuffed up when running in VMWare in the initial stages of the GUI mode (before driver install), as shown in my post down the page further. When removing components, make sure to leave in the language you need, as I think that was one of the reasons why it was stuffing up. Don't add the PnPDriversPath line either if integrating the drivers, as that's another reason for my error message I think.
  12. Difference between Symantec Anti Virus & Norton An

    I seem to remember seeing this question on here not too long ago, and I think I replied to it as well - Symantec (8.1/9) is more business orientated, with server/client usage, whereas Norton (2003/4/5) is more for home usage.
  13. Registry Tweaks

    Here's the Logon tweaks that I use in my regtweaks file - I think some might be not so common ones. ;--------------- ;Logon Tweaks ;--------------- ;Set information for above name and password in logon prompt [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "LogonPrompt"="Insert text to appear above name/password" ;Disable Welcome Screen and uses Classic Logon [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "LogonType"=dword:00000000 ;Set custom logon box [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "GinaDll"="custom msgina.dll file" ;Set logon box background image [HKEY_USERS\.DEFAULT\Control Panel\Desktop] "Wallpaper"="image source" ;Enable Ctrl+Alt+Del [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DisableCAD"=dword:00000000 Hope they can be of use for some people.
  14. SAV vs. NAV ?

    SAV9 is the corporate version - usually used in business environments as can run off a local server running the server version (downloads definitions, etc and clients access that instead of separately getting updates off the net). 2004/5 is the basic "home" version, designed for normal people running it as a standalone program and updating when they're online. At least that's what I can tell from using both in the past. Just try each and see how they work for what you want to do with them.
  15. Automatic Logoff

    I just add the following reg entries as a .reg at the end during the cleanup.cmd file and it works fine. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AutoAdminLogon"="0"