OK, sounds to me like ahcix86.sys is being called inappropriately.  JakeLD would know more about this than I.
As to VirtualBox, if you have the latest version installed (3.0.2), click on "Settings" then "Hard Disks" tab on the left, then uncheck "Enable additional controller" and see if that helps.  At the very least, you should be able to install Win2k in VirtualBox and get your code sorted.

Excellent first post!
Welcome to DriverPacks!
I edited your title to be more descriptive and added code tags to the post.

newsposter wrote:

Driverpacks officially supports XP only.  AFAIK no XP driver will function on Win2k.

That's not true.  Granted, the bulk of our drivers are oriented for XP, but many pull double-duty and work with Win2k.
JakeLD just built a new dpms release candidate that addresses your issue (maybe).  Can you test?

Fixed
-Changed [AM] & [AM1] sections to fix a BSOD with AMD IDE driver (cfp)

http://driverpacks.sytes.net/driverpack … 2_907r2.7z

If that doesn't work, newsposter is right I fear.  Win2k is beyond it's end-of-life, so your best bet is to run it in VirtualBox when needed.  Otherwise you can run Win2k on your older system where it was perfectly happy.

2,803

(10 replies, posted in Other)

Actually, that is very easy to fulfill.
For RIS, all you need is your own DNS server, a separate RIS server, and RogueSpear's AutoImage (no longer in development, but still available for now).
My multi-OEM OEMSCAN addon was developed exactly to meet your requirements.  And it doesn't require the COA keys (because they're not valid OEM SLP keys anyway).  And it's 100% legal because it uses M$ own activation mechanism. smile

2,804

(32 replies, posted in Other)

Well, WHQL status doesn't mean what it used to unfortunately.  Do you honestly think M$ tests those drivers on every conceivable hardware combination?  I don't! wink
Besides, the WHQL status means those drivers were tested "as packaged".  We don't redistribute those drivers as the manufacturer intended, so we incur additional testing hours.  Besides, have you seen some of the nvidia drivers that got WHQL'd?  h*ll, M$ even granted WHQL to BETA drivers!  WTF?

Sometimes a vendor will release drivers for 4 or 5 HWIDs, but we know they'll work with about 50 HWIDs, so we need to test the remaining 45 HWIDs to ensure stability.
That's the nature of the beast.

Wow, I'm actually shocked. yikes
It's been nearly a week and we haven't had a single post here with results!
I've personally had great success with both sound DriverPacks on the following hardware:
Asus Xonar DX
Realtek HD Audio, Desktop
Realtek HD Audio, Laptop
Realtek AC97 Audio, Laptop

But I am only one man with limited access to hardware.
WE NEED TESTING REPORTS!

Well I had a look at a borrowed WHS disc and it has a hybrid layout.  It has a \sources\boot.wim for the PE just like Vista, but then as you pointed out it has a \svr_2003\i386 folder with all the files you'd expect from 2003 server. 
Adding DriverPacks as method 2 shouldn't really be that difficult I would think since the files DriverPacks BASE modifies are right there..  Just point to the nested folder. 
But textmode mass-storage might be completely different since it uses the boot.wim like Vista.  And yet it has our typical dosnet.inf and txtsetup.sif files.
Hmmmm...

mr_smartepants wrote:
temporalwar wrote:

I would love to be able to mount a drive from a bad OS and extract the OEM SLP KEY, the activation files and all the system drivers

I've got the exact tools you need.  Let me package them up and upload them.  I'll post a link here.

I uploaded the files.  Click on the link in my signature (OEMSCAN...).  The archive is at the bottom of the very first post in that thread. "Grab_files.7z"

I'm actually looking at buying an HP mediasmart WHS for my home so adding this functionality would be in my best interest soon.
big_smile

Welcome back Jake! smile

Doh! You're right, I was wrong.
My apologies to you.
Google & wikipedia are indeed trusted friends now. wink
It's possible that if the disc folder structure is different than 2003, that DriverPacks won't work.  DriverPacks isn't advertised to work on Home Server.
I'll have to get ahold of an evaluation copy and see what the differences are.  OverFlow would have to make the modifications to the code to support it though.

Your post doesn't even make sense.  Win Home server is based on Vista/Server2008.  RVMI won't work with that.

2,812

(13 replies, posted in DriverPack Sound)

Did you try the new 907rc1 DriverPacks?  Major may have already fixed your problem. wink

2,813

(10 replies, posted in Other)

OK, I understand your position, but try to understand ours.
Your problem is neither DriverPacks related nor is it a problem when using DriverPacks with universal imaging.  That's why I moved the topic to "Other".
Your problem is product activation...period.

First, you need to determine what media type & key you're trying to install.
Link #1
Link #2
Link #3
The product ID can be found in your installation source CD in \i386\setupp.ini

If in fact you are installing a Retail version of XP, then each machine will have a unique activation key and must be activated over the internet or phone.
A VLK (Volume License Key) version of XP uses a single key to unlock a fixed number of machines (10, 100, 1000+) and the machines require no online activation.
OEM SLP (System Locked Preactivation) versions of XP use several key files to lock a copy of XP to a specific manufacturer (HP, Dell, etc.) and these machines are preactivated during XP setup and require no online activation.
All versions require validation to access MU/WU and it is this WGA validation process that you are failing which means that somewhere along the line you are not following the rules regarding activation/licensing.
The MAR program is actually a great benefit to the community and at a great price point.  It's a blend of Retail/system builder OEM license/media.  I'd be interested in seeing what they include in the OPK (OEM Preactivation Kit).

So once you determine what type of XP you are installing, then we can help you with your activation/validation issues.
Just so we're clear, we WILL NOT help you engage in piracy or other illegal acts.

temporalwar wrote:

I would love to be able to mount a drive from a bad OS and extract the OEM SLP KEY, the activation files and all the system drivers

I've got the exact tools you need.  Let me package them up and upload them.  I'll post a link here.

It's been over a year since we last released Sound DriverPacks!  We're a bit overdue for a release don't you think? smile
Two of our testing team members have devoted a lot of work renovating these packs.  Many thanks to Major.  I helped too. smile
Because there's been so many changes to thess DriverPacks, we need lots of testers. 
So, we're opening up testing to you! Our loving public. smile
But please remember, that these are Release Candidates, and not Releases.  Try not to deploy these into a production or critical environment.  We're releasing these for testing purposes only.
Please report back successes & failures to this thread.  The sooner you get those reports back to us, the sooner we can make these a final release.
Thanks, and enjoy the fruits of our labor.

DP_Sound_A_wnt5_x86-32_907rc1
MD5: 47f10520fb5e8ba9456ce62ce8cbbbe7
Size: 133 MB
Download: http://driverpacks.sytes.net/driverpack … _907rc1.7z

Changed from 8.05 release:
CR0\ -X-Fi Titanium PCI-Express
  Updated to DriverVer 02/19/2009, 6.0.01.1346 (2_17_0006)
CR1\ -X-Fi Fatal1ty
  Updated to DriverVer 06/03/2009, 6.0.01.1373 (2.18.0013.7)
CR2a\ -X-Fi Extreme Audio PCI-Express
  Updated to DriverVer 05/21/2009,5.10.0.209 (1.04.0000)
CR2b\ -X-Fi Extreme Audio PCI
  Updated to DriverVer 03/03/2008, 5.12.01.621 (1.04.0079)
CR3\ -Audigy
  Updated to DriverVer 03/04/2009, 6.0.01.1370 (2.18.0010)
CR4\ -SBLive
  DriverVer 06/13/2007, 5.12.01.514 (1.04.0077)
R1\ - Realtek AC97
  DriverVer 09/24/2008, 5.10.00.6300 (R4.06)
R2\ -Realtek HD Audio
  Updated to Driverver 07/06/2009, 5.10.0.5888 (R2.28)
R3\ - Realtek ATI HDMI
  Updated to DriverVer 06/24/2009, 5.10.0.5880 (R2.28)   
V1\
  DriverVer 06/10/2008, 5.12.01.3654 (5.40a)
V2\
  DriverVer 06/27/2007, 6.14.01.4200 (7.00b)
V3\
  DriverVer 10/16/2007, 6.0.01.1400 (5.00b) 
V4\
  DriverVer 05/19/2008, 6.0.01.1460 (5.60c)
V5\
  DriverVer 10/22/2008, 6.0.01.1550 (6.50a)

DP_Sound_B_wnt5_x86-32_907rc1
MD5: 7baf0b32f7a0c52585d4cc485c2267d6
Size: 87 MB
Download: http://driverpacks.sytes.net/driverpack … _907rc1.7z

________________________________________
Changed from 8.05 release:
3ST\
  Added 13 folders:
  1 - AC97 WDM SigmaTel 11/15/2004, 5.10.0.3952
  2 - Fujitsu AC97 WDM SigmaTel 12/20/2001, 5.10.00.7159
  3 - AC97 chips: 9700-9766 WDM SigmaTel 09/03/2002, 5.10.00.3696
  4 - SigmaTel C-Major Audio 11/11/2004, 5.10.4251.0
  5 - SigmaTel C-Major Audio 04/18/2003, 6.14.01.3798 old-series
  6 - SigmaTel C-Major Audio 03/13/2003, 6.14.01.3774 intel-family
  7 - HDA IDT High Definition Audio (STAC9200-92hd700 chip) 02/27/2008,5.10.5881.0
      and added some new HWIDs to support Compaq Presario CQ40-324TU
  8 - HDA SigmaTel High Definition Audio 07/27/2006,5.10.5143.0
  9 - IDT High Definition Audio WaveRT Driver Disk DriverVer=02/23/2009,6.10.0.6159 to support Dell E6400 series
  10 - IDT High Definition Audio Driver Disk  DriverVer=03/12/2009,5.10.20001.0
  11 - IDT High Definition Audio Driver Disk  DriverVer=03/02/2009,5.10.6162.0
  12 - IDT High Definition Audio Driver Disk  DriverVer=06/03/2009,5.10.6209.0
  13 - Added Sigmatel-Major Audio tu support Toshiba Laptop Satellite A55-S1064
       Commented some duplicated HWIDs with R1\, 3ST\1 and 3ST\4
AS1\
  Asus Xonar DX from driverVer 06/23/2008, 5.12.8.1738 to 09/01/2008,5.12.8.1747
AS2\
  Asus Xonar HDAV1.3/Deluxe to driverVer 01/23/2009,5.12.8.1763
AV2\
  Cleared out massive HWID overlap with RealTek
C2\
  C-Media 8738/8768 from DriverVer 11/21/2007,(1.1.7) to  08/24/2008,(1.2.1)
  Commented some duplicated HWIDs with C7\
C6\
  Added C-Media Drivers to support some new HWIDs.
  Commented some duplicated HWIDs with R1\ and C\
C7\
  Added C-Media Drivers 03/18/2009,5.12.8.1734 to Support some new HWIDs and to update others.
C8\
  Added C-Media Drivers 10/01/2008,5.12.8.1747 to Support some new HWIDs.
CxC\
  Added to support Compaq Conexant DriverVer = 01/21/2008, 3.47.0.0
CxH5\
  Added to support HP Conexant DriverVer = 06/20/2008, 3.34.0.52
CxHD\
  Added Conexant High Definition Audio 07/28/2006, 3.11.0.51
CxHD2\
  Added Conexant High Definition Audio 07/27/2006, 3.26.0.0
CXL\
  Added Connexant High Audio chip 221 05/02/2008, 3.49.4.50 to support Laptop Lenovo 3000 N500
CXT\
  Added Conexant Audio driver 05/08/2009, 3.64.6.0 to support some Thinkpad laptops
CXTO\
  Added Conexant High Definition Audio 04/24/2008,3.47.1.50 to support toshiba satellite pro laptop u400-23x
IB6\
  Replaced by a new recent driver SoundMAX Integrated Digital HD Audio 12/02/2008,5.10.01.6540 to support some Lenovo Desktops.
N\
  Moved from DriverPack Sound A
NV\
  Moved from DriverPack Graphics A\N1
  Nvidia High-Definition Audio DriverVer = 01/22/2009,1.00.00.42
SIS\
  Replaced missing .inf
SIS2\
  Deconflicted HWID overlap with RealTek and Updated the file with some HWIDs that were not supported
SMAC\
  Commented some duplicated HWIDs with IB7\.
SMC1\
  SoundMAX for Compaq from 09/24/2001,5.12.01.3035 to 11/09/2001,5.12.01.3039
SMD1\
  Added support for Dell E6400
  IDT SoundMax DriverVer=11/13/2008,5.10.0.6124
SMD4\
  Commented some duplicated HWIDs with SMD5\
SMD5\
  Added SoundMAX Integrated Digital HD Audio Device DriverVer 08/22/2008, 5.10.01.5852
SMH\
  Commented duplicated HWIDs with SMH1\
SMH1\
  Added SoundMAX Integrated Digital HD Audio 02/05/2008, 5.10.01.5220 to support HP COMPAQ 6820S
SMV\
  Added SoundMAX Integrated Digital Audio 06/07/2004,5.12.01.5150 to support Asus P4V800D-X (Chipset VIA Apollo PT880 Ultra)
SMZ\
  Commented duplicated HWIDs with SMC1\

________________________________________
Deleted:
\SMD1: Contained the same HWIDs with 3ST\9
\Y: Contained generic HWID (pci\ven_8086&dev_2485) conflicted with Realtek/SoundMax
\zC: Contained the same HWIDs with 3ST\4
\zd: Contained the same HWIDs with 3ST\1
\zD3: Duplicate with z2\
\zF: Contained the same HWIDs with 3ST\3
\zi: Exact duplicate with z2\ and contained super-generics
\zP: Contained the same HWIDs with 3ST\5
\zS: Contained the same HWIDs with 3ST\6
\zS2: Duplicate with z2\
\zU: Contained the same HWIDs with 3ST\8

2,816

(10 replies, posted in Other)

Since this is an activation problem, not related to either DriverPacks or universal imaging, I'm moving the thread to 'Other'.

2,817

(2 replies, posted in Feature Requests)

I agree.  There are times when I run SAD when the decompression process (on a slow machine) is agonizing.
I'm sure we can come up with something for the batch file.

2,818

(10 replies, posted in Other)

In your situation, a volume license may actually be better.  Expensive, but easier.
But if you're willing to do the research, the OEM SLP method would be the cheapest method if you're installing the OS that's listed on the COA sticker on each machine.  Perfectly legal and it's M$ preferred method.

Actually, thinking about it, you may not be able to purchase an XP volume license because M$ dropped it from active support.  If you're lucky, you may still be able to purchase a TechNet subscription to include XP.  But you might have better luck migrating your fleet to Win7 since it's so awesome.

2,819

(10 replies, posted in Other)

You can only activate a "Retail" copy once with any given key.
That's your problem.
If these are OEM machines (COA sticker on outside), then use my OEMSCAN addon to validate using SLP key method.

And this has nothing to do with DriverPacks.
...case closed...

All the drivers are expanded from disc-based installs to %systemdrive%\D\.
Once the installed system uses/installs the drivers it needs, DriverPacks Finisher then deletes the entire %systemdrive%\D\ directory and everything in it.
Unless of course you enable KTD (Keep The Drivers), which we do NOT recommend.

2,821

(24 replies, posted in DriverPack Graphics)

You could try adding a line to the DriverPacks Finisher .ini to do that work for you. wink
I'm not sure of the contents of your cmd file, but DriverPacks Finisher can do some of it for you.

exc_1_commands    = 3
exc_1_command1  = "regedit /s %systemdrive%\nvidia.ins"
exc_1_command2  = "cmd.exe /c DEL /F /S /Q %SystemDrive%\nvidia.ins"
exc_1_command3  = "cmd.exe /c copy /y %DPSROOT%\D\G\N1\nvhotkey.dll %SystemRoot%\system32"

2,822

(18 replies, posted in News)

big_smile

2,823

(18 replies, posted in News)

? ? ? ?

2,824

(6 replies, posted in Installation Platforms)

BadPointer wrote:

I have Windows XP x64 and it appears there is no driverpack for this system yet.

Oh please for the love of God do NOT bring up that old chestnut again! sad
I'll refer you to this post, specifically the last page.
http://forum.driverpacks.net/viewtopic. … 51&p=4

Short version= zero support for x64 XP.

2,825

(6 replies, posted in Installation Platforms)

I was going to edit it, but what's the point.  Like OverFlow pointed out, it's all on the DriverPacks description.