htc

all the usb drivers are PnP drivers and you can "unattended" install it - be sure turn on the print and connected to computer.

Many experts would say "No way!" because every drive on floppy root dir has the file "oemsetup.txt" and it will be overwritten if you copy scond driver onto it. But if you are a hacker(or will be such one) you can try to merge the content of two or more "oemsetup.txt" properly and near your goal.

The theme "InstallShield packed cabs" has been discussed thousend times in this forum. Use the search button to get more. All the .cat files are digitally signed by M$ to ensure the driver files(*.inf, *.sys, *.dll etc.) 1) authentical: the original files by the manufacturer and not infected by virus etc. 2) hardware compatible with MS Windows You cannot create those files by yourself - but without those file works your driver as good as you have them - only not signed (by M$).

All drivers for this audio codecs are in folder \wdm\ - you dont need to extract anything!

windows 98 resource tools

You have to install the print port driver for the USB "DOT4_001" first, then run your printui.dll to add the printer at that port...

Nothing, he put his post just in wrong place...

the "JO.SYS" only works for windows 9x/me bootdisks. It is useless for the topic in this forum. If you construct you boot menu with cd-shell v2.0+ you can implement a countdown with a message, before you load the menu.

A quick workaround: partitioning your hdd with a extern tool like symantec partition magic or acronis utilities. Then put your AIO-cd into computer and start it. On driver selection, choose the existing primary ntfs partion and no formating.

first, you have to put the RIGHT/PROPER driver files on the setup cd. second, the load order must be followed. Important: the windows setup sort the driver folders from winnt.sif by name, before put it into the reg-hive. This is the generic principles, nothing else.

If you have deleted the driver.cab or ripped out some driver by using nLite or so you will be asked for giving the driver path(or i-net searching) because windows cannot find the proper diver in its environment.

Witch "AC97 audio driver"? Witch "gigabyte mother board"? Your answer must be exactly, every alphabet can be important.

You have to integrate the chipsets driver first(the proper driver for the mb) and then the video driver, both in the folder order 01_chipset\*.inf,*.cat, 02_video\*.inf,*.sys,*.dll ...

tell us what driver did you want to integrate.

What is IDE SW-driver?

In Windows 98se you can also use the new wdm driver, so go ahead to the manufactor's site and download the new wdm driver. Then uninstall the old driver in device manager, use "Advanced hardware Editor" to delete the rest registry entries and finally install the new one.

Yes, I know... if this is the only way to make it work... what do you want to do anything else? But I dont have the SiS hardware, I cannot verify if it is neccessary, so only other members can tell us more...

wneto, I've a solution for your problem, please try it and report the results: in txtsetup.sit make following attachment: [SourceDisksFiles] sisraid.sys = 1,,,,,,3_,4,1,,,1,4 sisraid2.sys = 1,,,,,,3_,4,1,,,1,4 sisraid1.sys = 1,,,,,,3_,4,1,,,1,4 property.dll = 1,,,,,,,2,0,0,,1,2 [HardwareIdsDatabase] PCI\VEN_1039&DEV_0180 = "sisraid" PCI\VEN_1039&DEV_0181 = "sisraid1" PCI\VEN_1039&DEV_0182 = "sisraid2" [SCSI.Load] sisraid = sisraid.sys,4 sisraid1 = sisraid1.sys,4 sisraid2 = sisraid2.sys,4 [SCSI] sisraid = "SiS180 Raid/IDE Controller" sisraid1 = "SiS181 Raid Controller" sisraid2 = "SiS182 Raid/IDE Controller" Then copy the compressed sisraid.sys and property.dll (sisraid.sy_ / property.dl_) into your i386 folder. Dont forget put the PnP drivers in $OEM$/$1/Drivers and make a entry in winnt.sif ... Please test this combi of all sis raid controllers(180,181,182 = 964,964p,965)

the .vxd file is a driver for windows 95 and 98, from windows 98se on upto windows me you can use the wdm driver with .sys as filename extension. But in this we discuss only the setup of windows 2k/xp/2k3, in those os only wdm drivers(.sys) are valid.

The newst from Realtek(april 2005) worked fine for me on a asus mb but the second-last one didn't. If we use the driver shipped with the mb, witch was 2 years older(dated 2003) but has more option for 3D-Sound config.

I dont think [SCSI.load] SISRAIDP = sisraid.sys,4is correct, it must be: [SCSI.load] SISRAID = sisraid.sys,4 Furthermore, you may have to force the setup to copy the property.dll into c:\windows\system32 folder on your hdd before the first reboot... I dont have a sis raid controller so I cannot verify the above but excuse me if i'm wrong...

The USB floppy disk drives are not guilty - rather than the bios of your NB. For the textmode driver you need a floppy drive witch "natively" supported by mainboard bios - such as all the one in your desktiop computers incl. LS-120 drive. For notebooks w/o a build-in floppy drive you must strickt use the floppy drive shipped with your notebook, then activate the option "USB FDD Legacy Support" in your bios. If you use a "guest" usb floppy drive it may not work because it has another hardware ID as the mainboard bios expected(the usb controller build-in in the drive must be the same with the "original" supported). To check if it works, just put a dos/win9x boot disk and try to boot the dos/win9x. cheers your hardware profi

AFAIK win2k3 and winXP use the same driver engine, so my suggestions are: 1) install your drive in windows xp first, to see if it is the right one. 2) if you 've got the right driver for xp, so it must be the setup excutable detected a "unknow OS"/"unsupported OS" then refused to install right driver. You can either 3a) wait for a new release of ATI, it may very long or even infinitive, because win2k3 is a server OS, not designed for multimedia products... or 3b) extract the driver manually, patch the inf if neccessary and install it by hand.

Member gmx did not mention the problem of "setup driver pathes", so your link may not solve the problem or anwser the question. Be cooler next time

Just one year ago I had the same question: If I want to integrate a driver in to the unattended setup cd, but dont know if the Windows Xo or the new SP1 or the later SP2 comes with native support? My first reaktion was: 1) get the hardware ID of the driver to be integrated(eg. PCI\VEN_8086&DEV_1234) 2) extract all files in the driver.cab, sp1.cab and later sp2.cab into a new dir. 3) do a search for the files *.inf, containing the text of our hardware IDs: if found, the windows xp has the driver/support alread, if not found, we need to integrate it into $OEM$\$1\Drivers But this method did not work - step 3) gives always negative answer regardless what you looking for. So I had to do a workaround: 3) copy(merge) all *.inf into a big .inf file, for SP2 we get a 38MB .inf file, then 4) do a search in the big .inf file for the string of our hardware ID This works for me - till now. Important: list all the device names of windows xp supported hardware does not solve my problem. Newer hardware may have the same name but another "SUBSYS_########" or ""REV_##"