Jump to content

redxii

Member
  • Posts

    272
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by redxii

  1. Try not removing any services. Disabling them is just as good if not better than removing them.
  2. I don't know anything about switches, some of the MU Catalog drivers don't come with a setup. I keep all the drivers on a CD and extract the files from the Softpaq files, and after install use Device Manager or a provided setup that came with the driver. You can probably find a newer driver on HP's website using the search or looking on driver pages for different models that have the same hardware. They don't even have an XP driver page for mine, yet they have XP drivers available for everything in my laptop, and I have to scrounge around for newer Vista drivers because they won't tell me that either. Anyway, the newer driver still predates SP3, the sound card's installer or installation through Device Manager and the resulting driver install works 100% fine on plain XP SP3. This is my sound card's Hardware ID found in the device's properties: HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30B7 SP34200 supports: HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30B7 HDAUDIO\FUNC_01&VEN_14F1&DEV_5045&SUBSYS_103C30BB so yours can only be one of those.
  3. My dv6258se has a "Conexant High Definition Audio" sound card and had no issues installing the driver in XP SP3. I am using 3.26.0.50 which is newer than sp34200 (3.26.0.0), and that driver is for the same device. 3.26.0.50 is from Windows Update/Microsoft Update Catalog. XP SP3 already has a driver for the "Microsoft UUA Bus Driver for High Definition Audio", listed under System devices in Device Manager. As for the modem, it works, but I stopped installing the driver for it since like many other people we don't have landline service.
  4. I suppose this might also work: [-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Applets\Tour] [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Applets\Tour] "RunCount"=dword:00000000 the .DEFAULT is not necessary, it should read the HKLM RunCount first and go only by that, and it won't bother with writing anything to HKCU, but if HKCU one is present then it might override the HKLM one.
  5. You can disable the language bar with just this: [HKEY_CURRENT_USER\Software\Microsoft\CTF] "Disable Thread Input Manager"=dword:00000001 [HKEY_USERS\.DEFAULT\Software\Microsoft\CTF] "Disable Thread Input Manager"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run] "CTFMON.EXE"=- [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Run] "CTFMON.EXE"=- ctfmon is for typing in Japanese or other east asian languages, if you merely want to view Japanese text then you don't need it. As for Tour, do you add it after setup? I edited my hivesft.inf to add only the HKLM key during setup and the Tour doesn't appear.
  6. Open nLite and select every component. Can't guarantee it'll be functional, though.
  7. The "best" way to do those three is a matter of opinion then. I integrate SP3 the using update.exe switches, apply an update pack (I actually have my own SP3 update pack) using the RyanVM Integrator, then use nLite. RyanVM probably has much more control and undoubtedly access to the source for his integrator, while I doubt nuhi would let anyone else see his. nLite tries to duplicate features of RyanVM Integrator, but RyanVM can't guarantee that it will act the same or that nLite implements new features fast enough. My update pack has to do something special for XP Home only and is in a folder called 'home', apparently nLite does not pick this up, so Home users end up with all sorts of file copy errors because nLite missed something vital. I don't make any workarounds to fix nLite's behavior.
  8. You don't *have to* use RyanVM Integrator to integrate SP3. I used the update.exe switches, just be sure to integrate while running XP and not Vista. My guess is that most "slipstreamers" just use the update.exe switches but automates the process for the user. You should make an ISO or CD with SP3 integrated, make sure it works, then keep it in a safe place so you can reuse it and not have to integrate SP3 again when you need to start all over again w/ nLite or other addons.
  9. I'm guessing Pro retail. Based on OEM is "OEM", volume license is something higher like 640, and there is a program called "WGA Diagnostics" that produces reports like this: http://social.microsoft.com/Forums/en-US/g...1-9150b17c4159/
  10. That doesn't work unless you already have admin, and if you already have admin then having SYSTEM privileges is not that big a step up.
  11. redxii

    Slipstreaming SP3

    You only need SP3, I recommend to do the slipstreaming in XP even if nLite can 'fix' it in Vista. I compared XP Pro SP3 integrated by MS to a gold CD, slipstreamed the gold CD using only SP3 and the install and the results were the same. I used the 'official' method extracting the SP file and doing the update.exe switches, in XP. The CD key install issue was a result of using Vista to slipstream and probably a coincidence you received the fix from nLite rather than from doing SP1a then SP3.
  12. Did you delete the i386\WIN9XMIG, i386\WIN9XUPG, and i386\WINNTUPG folders? They aren't needed if you're doing a clean install. You can also delete DOTNETFX, Support and ValueAdd folders.
  13. XP SP3 requires that SP1 or SP2 be installed, or SP3 can be integrated w/ no prerequisite service pack on the slipstreamed source. It's not uncommon to have a CD writer.. I integrate SP3 of course, instead of wasting time installing previous service packs. Vista SP2 isn't exactly cumulative either, it will require SP1 because they were too cheap or lazy to make a separate service pack for Server 2008.
  14. My Hulu.com-OnlyinVista-skipping machine is a Turion X2 TL-56, 2GB of RAM and a GF Go 6150 w/ 128MB of RAM. It came with Vista. The newest signed driver for it is 167.43, compared to 86.38 in XP. Vista has plenty of free RAM to work with there is no excuse.
  15. vLite can help, but in the end there is only so much that can be done and Vista will never be as fast as XP. I wanted to watch a video on Hulu.com and it skipped and stuttered on 480p video to no end on Vista (w/ DWM/Aero Glass disabled and using Windows Standard theme). So I ditched it again for the n'th time and put XP back on. XP plays as smooth as butter even on 720p... and I don't even use nLite at all. I will give SP2 a try when it is finished but it'll probably still be disappointing. Then again if you have a really, really high-end system with like 20 cores and a petabyte of RAM you probably wouldn't notice the massive increase in Vista's overhead and losing a few of your 100000 frames per second.
  16. KB951376 updates bthport.sys, but Windows doesn't copy it to the drivers folder unless you have bluetooth devices, and so it sees the missing file and thinks the hotfix isn't installed. Driver.cab should have the updated file but it doesn't check driver.cab. nLite has a fix for KB951376.
  17. You can replace the default task manager with process explorer without replacing taskmgr.exe. Look in the process explorer menus and there's an option there, it creates the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\taskmgr REG_SZ key called "Debugger" and the value the path to procexp.exe, every time you launch taskmgr.exe it'll launch procexp.exe instead.
  18. You mean how when you open the command prompt, it isn't themed? MS offers this: http://support.microsoft.com/default.aspx?...kb;en-us;306509 so perhaps it is the same for those error dialogs.
  19. I'm confused, you want *no GUI* or an alternative GUI to Explorer? Linux has a fully functional command line and any window managers or window systems are completely separate can be completely removed so as to not have to use any resources for them or crash your server. Since I take the application is for personal purposes, grab Ubuntu Server edition. Ubuntu without a GUI, but still has a very easy package manager.
  20. With billions of moolah, MS can't get the web setup or download server to work correctly or something. Whatever it is you need from the web setup can be found in the latest redistributable, they are the same thing except the web installer being a little more intelligent to download only what's needed/not already installed. http://www.microsoft.com/downloads/details...;displaylang=en
  21. redxii

    SP3?

    SP2 w/ all updates should be just as good as SP3. Installing a service pack is a major update and might just cause problems on a stable system. I always do a clean install with the service pack integrated if I want to upgrade to the next service pack. As for IE.. your call. Just keep it updated. IE's rendering engine can be used in just about any application and is what Windows Explorer or WMP use, so you're not in the clear just because you don't open the blue IE icon.
  22. System.ini and win.ini can be found in the i386 folder and are copied like all other files. SYSTEM.IN_ & WIN.IN_. If you just plain delete them from the disk you will get a file copy error. Don't delete ntkrnlpa.exe, that is your kernel.. command.com is 16-bit, since you already removed 16-bit support command.com can no longer function. It is NOT needed, nor was it ever at anytime used, for batch files (.bat).
  23. If you removed 16-bit support then you don't need system.ini nor win.ini and can safely delete them. Although, they are just text files they take up a pittance of space. If you remove 16-bit support, NTVDM is DEFUNCT. Programs that need system.ini won't be able to run and therefore there would be no need for them anymore. I've even removed autoexec.bat, config.sys, msdos.sys and io.sys from the root of the drive. Someone said Windows wouldn't boot after deleting these files, they were probably running 9x/ME where it's actually required. I wonder who here thinks "ConservativeSwapfileUsage=1" works in NT-based Windows (i.e. XP).


×
×
  • Create New...