Bâshrat the Sneaky

OK, keep on testing Bâshrat the Sneaky

Current status TXTSETUP.OEM method drivers added: -ACARD > ALL -ADAPTEC > ALL -NVIDIA > ALL -SILICON IMAGE > 3112r Just to let you know I'm still working on the DriverPacks! Bâshrat the Sneaky

You should place the cmdow code at the top of your batch file. About deleting itself: I don't know... Try with removing the EXIT statement in the cleanup.cmd. Bâshrat the Sneaky

Probably you've forgotten to use the /WAIT switch after the START command: START /WAIT and that would be why Install.cmd isn't finished when Cleanup.cmd starts. Note: Your folder names aren't identical About hiding DOS windows: google for CMDOW, or take a look at the guide, it's covered somewhere inthere. Use: CMDOW @ /HID Bâshrat the Sneaky

No, that's correct! There shouldn't be anything in the $OEM$\$1\Drivers folder! Please check if the drivers themselves did get installed! EDIT: forgot to say this you shouldn't add that line to your winnt.sif, because it's already included in the presetup.cmd file. (that you won't notice, but it's being processed by the RUN_ME_METHOD2.cmd file!) EDIT2: well the edit above is totally wrong! I must have been sleepy or something The problem must lie in the fact that the DriverPacks aren't being decompressed properly! Please verify that! Bâshrat the Sneaky

Hi, I'm using GMail Drive for Windows, does anyone know what I might be doing wrong? I'm a 100% sure I entered everything correctly! I've been searching the net for solutions, somewhere it's been said that your username can't be too long, I made another account with only 6 characters, which is the minimum and still no effect... Can anyone help me out? Bâshrat the Sneaky

OK, when I'm working on the Sound DriverPack, I'll let you beta-test it Currently I'm working on DriverPack MassStorage... Bâshrat the Sneaky

According to [url="http://www.microsoft.com/technet/prodtechnol/winntas/deploy/depopt/gdautset.mspx"]this article[/url], you can't make subfolders in the TEXTMODE folder. Can anyone proove otherwise? (By this I mean, doesn't anyone know a work-around or something?) EDIT: It's been tested and it doesn't work... :'( anyone ideas? (I don't like messed up folders!) EDIT2: then why ARE there subdirectories for some drivers? e.g.: Adaptec SATA RAID 1210SA driver's txtsetup.oem: [code][Disks] d1 = "Adaptec Serial ATA HostRAID Driver Ver 1.00 For Windows 2000/XP", \hraidsk1, \Win2000 # directory # Specifies the directory on the disk where the installation files are # located. The directory must be specified as a full path from the root and # must not specify a drive.[/code] EDIT3: found why it wasn't working also in the same txtsetup.oem: [code]# tagfile # Specifies the name of a verification file on the disk. The filename must # be specified as a full path from the root and must not specify a drive. # Setup checks for this file to ensure that the user inserted the correct # disk.[/code] going to retry with subfolders now...

I'm sure this has been covered before on this forum! Did you use the search function already? Bâshrat the Sneaky

I'm in the process of converting all drivers of DriverPack MassStorage to a new method. Untill that version is released, please follow GreenMachine's Guide! EDIT: forgot to say this: the problem might be that SP2 doesn't allow this driver to be installed, so are you using Windows Service Pack 2? Bâshrat the Sneaky

Well that might be a typo, or it must have changed. (I've tested it a couple of times and it worked, but it's been a long time since... so....) This .vbs script is a script I made myself because any silent switches didn't work properly... Looking for the file now, I'll attach when I've found it! Bâshrat the Sneaky EDIT: found the file, hope this helps some... iTouchl.vbs

Of course I am. All the time I've been thinking this error was being caused by the SoundMAX drivers, but apparently the problem lays in the Realtek drivers. The good news is that Realtek has released new drivers (version 3.65), the bad news is I don't know if this will change something about this error... Let's hope so! Bâshrat the Sneaky

In fact you're asking two questions: 1. Why do both drivers get installed? > There's no other explanation than there are two sound cards detected, which means he didn't disable it properly 2. Why doesn't it produce sound? > Please check if all cables are connected properly, if it isn't muted and so on. This driver has been confirmed to be working before! Bâshrat the Sneaky

Did you set any network preferences in your winnt.sif?

I don't think you're in the right forum for that... But hey, maybe there's someone who knows more about this? And what kind of DLL files would you like to make? Hacked driver dll files or something? (because you've posted this in the Device Drivers forum...) Bâshrat the Sneaky EDIT: a leet number of posts

Did you add the necessary entries to the dosnet.inf file? (in case you're adding MassStorage drivers)

@Zilexa: posting that in ONE of the topics would have been suffisient! Please stop doing that! Bâshrat the Sneaky Device Drivers forum moderator

Have I said that the DriverPacks support chipsets? No, I haven't! DriverPack ChipSet might be coming in the future, but it isn't available yet! So you still have to add all chipsetdrivers yourself! P.S.: Deleted your double post.

What if you'd have done the effort of checking my website? Then you'd have seen this page, that lists the manufacturers. And maybe, just maybe the changelog would include the entire list? Search better next time Bâshrat the Sneaky

I'm looking for some people to be beta-tester for me. As you may know, several MassStorage controllers aren't being installed properly at the moment. Well, I'm trying to fix this now. Requirements: -the will to test the beta-package several times. -CD-RW's -you don't have to be experienced with this -having a spare harddisk (just to test the install cd) is an advantage What do you have to do? -download a SFX archive (I'll provide you with the link) -extract it -copy the files to your source (the folder that contains the I386 and $OEM$ folders) -burn it to the CD-RW >>5 minutes -reboot your pc with this cd and see if it works If you're interested, please send an e-mail to this address: betatesting (at) btsunattended.net Subject: [bETA testing] Don't forget to mention your controller! Bâshrat the Sneaky

Actually, the final ISO will be smaller if the files are not compressed. Why? 'Cos the UltraISO 'Optimize' option will be able to match the identical files and only use one copy. Hmm, is there a single batch command that can copy all the .sys files from the $OEM$\$1\Drivers\M\... to I386 in one go? Not many people use that function (as far as I know at least) Bâshrat the Sneaky

You can run that from GUIRunOnce or RunOnceEX, anything as long as Windows is loaded (not tested, but I'm convinced that's a requirement). You should add the drivers to your CD as described in the guide, so the base drivers get installed short explanation: IF EXIST driverfile ( ECHO blahblah START /WAIT %VARIABLE%\path\SETUP.EXE /switches REGEDIT /S %VARIABLE%\path\SETTINGS.REG ) This .reg file contains the settings I've set and I import them so I don't have to set everything again . I hope this helps you! Bâshrat the Sneaky

I think we will have to try if the SiI3112 SATARAID driver also supports the SiI3112 SATA Link controller... I'm currently working on a huge update for DriverPack MassStorage, which (currently only partly) switches to the textsetup.oem method. If someone sees the light, please let me know, but I don't see any method to determine which driver should be used when we're stuck with 2 identical DeviceIDs... For those who didn't know yet, this article may be interesting. It includes the statement that you should use the BASE drivers when you are using a single disk, even when you're using the SATARAID controller! Bâshrat the Sneaky

Thanks for your efforts RogueSpear!

To everyone who's experiencing this problem: Please try again, after removing the $OEM$\$1\Drivers\S\SM\I folder and $OEM$\$1\Drivers\S\SM\SM.exe. This removes the IBM driver, as well as the control panel. Please tell me if the error still shows up! @DigeratiPrime: huh? The Realtek drivers ARE inthere, you can check it yourself! Are you sure you had OemPreInstall=Yes and the OemPnPDriversPath in your winnt.sif? Bâshrat the Sneaky