I guess I wanted to have the OEM in the $OEM$ so I didn't have to copy the OEM folder manually to the root of every computer I wanted to install WinXP onto. Installing from a USB key is sweet stuff thanx to Driverpacks and RVM.
2 2006-11-08 15:14:02
Re: [unsolved]oem or $oem$? (14 replies, posted in DriverPack Mass Storage)
I'm sorry, I should have mentioned that I was installing from a USB key. I put the $OEM$ direction I created in the i386, so it copies the OEM directory which is inside the $OEM$\$1\ to the root on the partition I am installing the OS on to.
I never got method 2 to work the way I needed any other way.
Sorry for not being clearer.
3 2006-11-08 11:07:26
Re: [unsolved]oem or $oem$? (14 replies, posted in DriverPack Mass Storage)
I used method 2. I created a folder called $OEM$ and a folder within that called $1. I then copied the method 2 OEM into $1 and that was it.
4 2006-10-22 16:23:26
Re: [NEEDS REPLY] Promise SATA 378 not detected during text mode setup (14 replies, posted in DriverPack Mass Storage)
Here's my $.02.
PCI\VEN_105A&DEV_3373&SUBSYS_80F51043&REV_02\3&267A616A&0&40: WinXP Promise SATA378 (tm) IDE Controller...is my onboard SATA378 chip on my Asus A8V. I didn't realize till later that the devices on the Promise SATA's weren't working. To get them to work, I tried many drivers, I had to settle on v1.0.0.27. The newer drivers on ASUS's website didn't work for me. The drivers that were even newer from Promise's website didn't work either. They would both come up with "This Device Cannot Start (Code 10)". Even a reboot, my devices still didn't come up. I also was checking in Disk Management.
When I finally settled back to v1.0.0.27, everything worked in Device Manager, but I had to "activate" the drives in Disk Management.
Where did I get the v1.0.0.27 drivers? Well I don't remember. I did a backup of my drivers a while back and can not find them on the web anywhere. I'm thinking I got them from ASUS's website but from a different motherboard that had the same Promise chip.
Here is the readme file that came with the drivers:
**********************************************
* *
* Promise SATA378 Driver Diskette *
* *
**********************************************
====================
Contents on the disk
====================
README TXT This readme file
ULSATA Microsoft Windows miniport disk label file
TXTSETUP OEM Microsoft Windows miniport text mode setup file
WIN2003 <DIR>
ULSATA SYS Microsoft Windows2003 miniport driver
PTIPBM DLL Promise Windows2003 set Pbm dynamic link library
ULSATA INF Microsoft Windows miniport setup file
WINXP <DIR>
ULSATA SYS Microsoft WindowsXP miniport driver
PTIPBM DLL Promise WindowsXP set Pbm dynamic link library
ULSATA INF Microsoft Windows miniport setup file
WIN2000 <DIR>
ULSATA SYS Microsoft Windows2000 miniport driver
PTIPBM DLL Promise Windows2000 Set Pbm dynamic link library
ULSATA INF Microsoft Windows miniport setup file
WIN98-ME <DIR>
ULSATA MPD Microsoft Windows98-ME miniport driver
ULSATA INF Microsoft Windows miniport setup file
PTISTP DLL Advanced INF file format support file
PU66VSD VXD Promise power management driver
SMARTVSD VXD Promise S.M.A.R.T. driver
NT4 <DIR>
ULSATA SYS Microsoft WindowsNT miniport driver file
PTIPBM EXE Promise WindowsNT Set Pbm execution file
ULSATA INF Microsoft Windows miniport setup file
================
Software Version
================
Microsoft WindowsNT miniport driver 1.00.0.27
Microsoft Windows2000 miniport driver 1.00.0.27
Microsoft Windows98-ME miniport driver 1.00.0.27
Microsoft WindowsXP miniport driver 1.00.0.27
Microsoft Windows2003 miniport driver 1.00.0.27I have the files if it comes up.
5 2006-10-22 15:11:38
Re: [IMPLEMENTED] Creative Sound Blaster Audigy 1/2/4, 2.09.0016 (3 replies, posted in DriverPack Sound)
I have a Creative Audigy 2 ZS Platinum. I would like to point out that when I used the DriverPack Sound A, sound did not work for me. In Device Manager, everything looked ok, meaning no !'s anywhere. I installed the drivers mentioned in the file above manually and sound worked then after.
Here is the specific HWIDs info about my sound hardware:
PCI\VEN_1102&DEV_0004&SUBSYS_20021102&REV_04\3&267A616A&0&70: Creative SB Audigy 2 ZS (WDM)
PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_04\3&267A616A&0&71: Creative Game PortMy $.02
6 2006-10-22 14:11:06
Re: The Driverpack freezes after Windows first run (9 replies, posted in Feedback and Support - DriverPacks Base)
Sorry, double posted some how.
7 2006-10-22 13:06:12
Re: The Driverpack freezes after Windows first run (9 replies, posted in Feedback and Support - DriverPacks Base)
I have/had the same issue. I did Control+Shift+ESC to bring up the Task Manager and ended the task named "setup.exe" instead of the finisher. When you do that, the finisher continues and finishes the rest of the stuff that it does. Unfortunately I deleted my log file already to show what should have been after your last line, but it may be related with your BSOD and other issues.
I believe that if you got an error launching CLI.exe, it has to do with you not having Microsoft .NET Framework installed. I'm not positive about that though. I uninstalled ATI's software (not the drivers) soon after.
Anyway, good luck.