Jump to content

Bâshrat the Sneaky

Member
  • Posts

    5,580
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Everything posted by Bâshrat the Sneaky

  1. Don't know about the logo. But I suggest you import that regtweak using cmdlines.txt, that way ALL users will inherit it!
  2. @Alanoll: a Distribution Share can also be the Share on your harddisk before you make an ISO of it and burn it to CD/DVD... At least that's how I've always understood it. (Check the Answer Wizard of MS in deploy.cab)
  3. It's a notebook!!! I'd start to do these things: 1. install newest drivers 2. install all Windows updates 3. if still no luck, RMA the notebook... EDIT: another test you can do is Memtest86+
  4. For network installations, the $OEM$ folder should indeed be INSIDE the I386 folder.
  5. hehe Chipset is coming tomorrow or the day after that A little patience and your problem will be solved
  6. T-13 is svcpack.inf, so I suggest you'd use T-12 to apply your regtweaks, which is cmdlines.txt. All info available on this page of the guide
  7. Well... if you use batch files and trying to hide them with cmdow.exe this is quite normal. If you don't want that, you'll have to use something else, like RunOnce, RunOnceEx, XPlode, WPI or something like that.
  8. To problem 1: open your dosnet.inf and change everything that's on CD2 to CD1, and then make sure you have everything on CD1. (you will need a 99min CD if you don't remove anything)
  9. Sorry, impossible... At least with normal methods... Probably you could do it with devcon.exe. I suggest you do some research on how to install drivers with that.
  10. Then... HUH The only cause can then be... file size checking... But normally it *SHOULD* work like this.... Anyone else has an idea?
  11. Aha... That makes the difference: you started setup through winnt32.exe and therefor you have to edit the dosnet.inf file. Please check if the aliide.sys file is included there!
  12. @ToasterMax: welcome to MSFN! Please go to the I386 folder of your share and check if the file 3wareDrv.sys is there. Secondly, tell me the path where you've put the DriverPacks BASE (the path to the batch file of the first step). @SaintLaur: Ehm.... I suppose those folders apply only for the additional programs like SurMix etc? I'll check Creative's site for your driver later. Do you want to INSTALL or to DECOMPRESS my DriverPacks from T-39?
  13. Please check if any driver files for these particular devices are missing!
  14. Hmm yes, I guess you're right there, RyanVM I'll do that. That way I won't have to update the changelog either... But note that you don't have to download all the DriverPacks, just the DPs BASE, which is only half a meg
  15. In what folder are these files?
  16. Please read the Stickied guide, and if you still have questions then, you can ask them here.
  17. Indeed, check the html files for all DriverPacks. Topic was posted in wrong forum, topic moved.
  18. DOH That's right Buletov! But not in all cases.. The omega's support lots of graphics cards the standard Catalysts (so also the ones included in Win XP) don't support. @nowarez: if you really want the omega's to install, you only have 3 options left: 1. conditional installation: IF EXIST %SystemRoot%\system32\driverfile.sys ( START /WAIT OmegaDrivers.exe /switches ) 2. regular installation START /WAIT OmegaDrivers.exe /switches 3. remove the ATI drivers out of Driver.cab (and still add 1.)
  19. I deleted the other topic . Please post the changes you've made to the txtsetup.sif file!
  20. It will really SLIPSTREAM the drivers into your Windows XP share, so yes, the drivers will be used during setup (no more F6 pressing)!
  21. I did not know about it either. But it seems that you have to add it to make it work properly... You can download it from the official site, i.e. www.siliconimage.com
  22. I said I wasn't sure... I'll try to find it back later today.
  23. @mark49: I was just making a joke... Renaming won't work. You'll have to add another driver But please wait for the new version of DP MassStorage, it will have the fix, and will become available within a couple of days.
  24. They're added now. But didn't you edit the dosnet.inf file?
  25. I suppose you don't want to run setup just like that? I.e., you don't want to install it as a regular application? Because then it will be installed always... If so, just extract the Omega drivers and put the driver files in a folder like you've read in the guide. Then point to them in the OemPnPDriversPath of your winnt.sif. But what I don't know is how to get the control panel installed as well. You'll have to do some research on that. Out of curiosity: why do you prefer the Omega drivers? If the official Catalysts are fine for you, you can use my DriverPack Graphics A, which will also install the control panel for you!
×
×
  • Create New...