Jump to content

vipejc

Member
  • Posts

    312
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    United States

Everything posted by vipejc

  1. How do I use nLite to integrate all XP Windows Updates from SP3 until today? Does this cause any problems?
  2. My plan is to use 32-bit Windows XP Home with SP3 for life, and I was wondering which users still use Windows 9x or ME as their only OS and plan to do the same? If so, is buying compatible hardware a challenge for you? The challenges are hardware support (motherboard chipset) and no anti-virus support. The older the OS gets, the harder it becomes to maintain. The reasons XP is my last OS: 1. Microsoft makes so little improvements to each Windows OS, it doesn't pay to switch unless you need an improvement. 2. Windows is so bloated, poorly designed, maintained, and behind the times. 3. It takes years to learn an OS, and the time and desire just isn't there to ever do it again. 4. Legacy hardware is cheaper and much more stable. 5. I spent seven years learning software and hardware to get XP spic-and-span clean, and performance is through the roof. (I can go over two years without a reboot, and did just to see how stable XP really is. I would've kept going but didn't want to risk a hardware failure and shut down the system for maintenance.) 6. I know my system like second nature and using, managing, and repairing it is a snap.
  3. vipejc

    ISO labels

    Just to be safe I changed it.
  4. vipejc

    ISO labels

    Is it necessary to change nLite's default Label from WinLite to the label of the Windows installation disc for the bootable ISO to boot? For example, change WinLite to GRTMHFPP_EN? I know that if the label of some Windows installation discs isn't an exact match, the disc won't boot. nLite doesn't warn about this, but I just want to be sure so I don't burn a coaster.
  5. That's what I did. nLite integrated VIAMRAID.INF as text mode, and VIAMRAID.SY_ is in the I386 folder. I'd say it's time to burn the ISO, wouldn't you?
  6. Both VIAMRAID.INFs are identical. Does this mean I can use either one regardless of if it's in the x86 or XP folder?
  7. Both copies of VIAMRAID.INF are 3 KB. If "txtsetup.oem" is in either the x86 or XP folder, nLite offers the text-mode option. I'm guessing the XP folder is correct because that's a subfolder of the drvdisk folder, which is the folder where all the files are stored that XP would read from the floppy disk after you press F6 to install a driver during setup. The VIAMRAID.INF in the x86 folder seems like it's the PnP version that the VIA setup program would install while Windows is online. Does it sound like I did it right?
  8. As I said, yes, I moved "txtsetup.oem" inside the XP folder. I did it a second time, and this time it worked. nLite shows Mode TXT. Am I ready to burn the ISO? Or, should I move "txtsetup.oem" inside the other folder with the other VIAMRAID.INF?
  9. How do I give nLite the text-mode driver so it shows Mode TXT, not PNP? It asked for the .INF, so I pointed it to VIAMRAID.INF. What am I doing wrong? Here's the folder structure of the driver package. I tried both VIAMRAID.INFs, but nLite shows both as Mode PNP. VIA_VRAID_Windows_V6.00a VRAIDDrv XP x86 x86/viamraid.cat x86/VIAMRAID.INF x86/viamraid.sys drvdisk x86 XP XP/viamraid.cat XP/VIAMRAID.INF XP/viamraid.sys
  10. Well, after seven grueling years, I've finally achieved a junk-free Windows XP. Now, I'm not talking about blindly deleting files and folders that aren't used today. This was an expert job in which I deleted all junk that's junk today and tomorrow. That means no installing new hardware in five years and Windows error-ing because years back I deleted a required driver. Now, to make the perfect backup image and relax for the rest of my life... The coolest part about this protect was I did it with no safety net (backup image), not one BSoD, or even an error.
  11. I used nLite to add a SATA RAID driver for my VIA chipset and create an ISO, but I'm not sure if I did it right. The mode is PnP, but shouldn't this be text mode? I then clicked the help icon, and nLite stated that if you were expecting a text-mode driver and it's not here, make sure you place the driver's "txtsetup.oem" in the same folder as its .INF. So I moved "txtsetup.oem" from the drvdisk folder to the subfolder XP where the .cat, .INF, and .sys files are. Did I do it right?
  12. Is it possible to create a SATA-future-proof XP install disc that contains generic Intel and AMD SATA drivers (AHCI and RAID)? Or, no because ACHI and RAID are Southbridge-specific and each controller or series of controllers require its own drivers? If that wasn't clear, in other words, I want a generic Vista-7 SATA driver for XP that will work with any SATA disk. A driver that will allow XP setup to detect any SATA hard disk and successfully complete installation. Is it possible to copy ataport.sys from Vista and paste it in XP's system32 folder, copy msahci.sys from Vista and paste it in XP's system32 folder, and copy pciide.sys and pciidex.sys from Vista, delete those files from XP's system32 folder, and paste Vista's pciide.sys and pciidex.sys in XP's system32 folder?


×
×
  • Create New...