OK, that gives me some info on where to start.  No promises though.

Ken@fri wrote:

Do u find any time to finish the experimental code below?

If yes, could u add a portion to build a multilanguage edition?

Yes I did.  And yes, I added a section to build a multi-language version.
Unfortunately, I built it under consignment from our sponsor LinMin.  They sell it now as the LIU (Found here)

I'll see if I can split the code off for a quick stand-alone script.  (no promises)

TechDud wrote:

Not working with Win2k.

In SAD3, change line#215 from this:

FOR %%i IN (2600 3790 2715) DO (IF /I "%F_BuildNumber%"=="%%i" SET "F_OSBuild=NT5")

to this:

FOR %%i IN (2195 2600 3790 2715) DO (IF /I "%F_BuildNumber%"=="%%i" SET "F_OSBuild=NT5")

I think 2195 is the build number for Win2k.

Still, it would be interesting to find a technet article which states where the hard-limit is.

Question posted here: http://www.wincert.net/forum/topic/1146 … imitation/
O_o

56

(3 replies, posted in Software)

Thanks for the follow-up Ian.  And welcome to DriverPacks!
Your tool looks like an interesting spin on an age-old problem.
We wish you the best of luck on your new tool.

I know what you're going through.  We lost our 14-yr old dog last year and I'm still getting over it.

muiz wrote:

Any one has the link to the latest SAD3 for me please?

Sorry,
The latest one wasn't in this thread.  I just uploaded it.
My apologies.
http://www.sherv.net/cm/emo/funny/2/banana-on-computer-smiley-emoticon.gif
v130627 Download:
:: v130627 v3.0 (Erik Hansen)
:: Added 7zip switch -aoa to enable auto-overwrite mode.
:: Removed Win8 leaked build numbers and added Win8.1 preview build number to detection array.
:: Added DIR to CDROM detection array to prevent errors with card readers in system

jlst wrote:

Thanks man. I really appreciate you continuing to work in this driverpacks

Indeed!  We all appreciate the hard work TechDud is contributing around here. smile

ChiefZeke wrote:

IntelRapidStorageTech12_8_0_1016.exe released

I beat you to it by nearly a week! wink

mr_smartepants wrote:

...and now RST 12.8 is live!  What happened to 12.7?

I know, I REALLY need to find some time and clean up the first post.  We have links all over the place.  Sorry.

OverFlow wrote:

SAD was my idea and original script (for XP) that mr_smartepants almost singlehandedly grew into it's current version

It's a team effort!
"If I have seen further it is only by standing on the shoulders of giants." -Isaac Newton

63

(5 replies, posted in Hardware)

skydec wrote:

My conclusion is that something is wrong with AMDFilter drivers package

Yeah, that's why I put this statement on the AMD Filter download page.

WARNING!
This 3rd Party DriverPack will cause BSOD if integrated into systems with Intel Graphics hardware.  It is meant for AMD/ATI systems ONLY.  Use at your own risk.

I don't know what to tell you.  It worked fine on the HP workstations I installed it on (AMD-based).

64

(5 replies, posted in Hardware)

How are you "installing" DriverPacks? 
You don't mention what method you use to integrate the drivers or "install" them after Windows7.
We also need your HWID list.  You can use the utility linked in my signature.
More details please...

bikerboy0507 wrote:

This is such a tedious process.

Yes, but when you're talking about deploying an image to a 1000 corporate machines, it makes sense to invest the time to build a single "perfect" image, then export/deploy that image to your entire company's workforce.
Besides, tools like RT7 Lite can't be used (legally) in a corporate environment.

"Installing" Windows to 1000 machines is mind-numbing and very time intensive.  Easier to build a single image and clone it 1000 times.  We're talking days of saved time, maybe weeks opposed to a traditional install.

66

(42 replies, posted in Hardware)

TechDud wrote:

One could be thankful that Gollum didn't feel the need to write in.

LOL, that was epic!

67

(12 replies, posted in Vista / 7 DriverPack Mass Storage)

...and now RST 12.8 is live!  What happened to 12.7?

68

(42 replies, posted in Hardware)

TechDud wrote:

negatively disparaging the character of mr_smartepants et al.

Oh, believe me I've heard worse.  I have a thick skin.  He (or anyone) can negatively disparage my character anytime they like.  I don't care. big_smile

I'm a firm believer that everyone is entitled to voice their own opinion...even if it's wrong. wink

Jeff and I are in agreement that we won't support W2k anymore.  Nobody will be able to convince me to devote any more time to that ancient OS.  Sorry, but I have better things to do with my limited time.  I'm also sorry that upsets you, but ranting won't change my mind.
If TechDud wants to take this on as a challenge, so be it.  But that is his choice.

silents429 wrote:

Again, I choose Windows 2000 for educational purposes not for general usage.

Since that is the case, why not just restore your Sony back to factory defaults for general usage and run Win2k in a virtual machine (VirtualBox, VMware, HyperV, etc.)?
You'll be much happier.

69

(3 replies, posted in Hardware)

Contact Apple support.

70

(42 replies, posted in Hardware)

silents429 wrote:

Cutting off support for those people seems unneeded and plain stupid to me.

Thank you for calling us "stupid".

http://en.wikipedia.org/wiki/Usage_shar … ng_systems
Windows 2000 usage is so low it doesn't even beat the "all others" category (less than 1%).

Try to look at it from our perspective.  We are trying to support the mainstream OS's because that is what the bulk of the users are using.  By comparison to any OS, Windows 2000 usage is insignificant.  That ship has sailed.
Now if you're looking to Win2k for a learning experience, then that is fine, but don't take your frustrations out on us.

None of the old Win2k drivers in dpms have changed.  Only the .ini structure has changed.  If I were you, I'd start with dpms 12.09 and work backward through the older DriverPacks until I found one that worked, then report those findings here (with your HWIDs).
At that point, someone with free time (of which I have precious little) can assist.

If none of the packs work, then you can set the BIOS to change SATA to IDE (Legacy mode) and it should be fine.

71

(42 replies, posted in Hardware)

Well, what did you do to make it work?  If your changes don't break anything for XP or other OS, then leave the changes in there.
If it's fixed, then it's fixed.  But I wouldn't waste any more time on 2000 support.

72

(42 replies, posted in Hardware)

silents429 wrote:

2000 is not dead.

Windows 2000 IS dead.
http://support.microsoft.com/gp/lifean35

Microsoft wrote:

On July 13, 2010, Extended Support for Windows 2000 Professional will end. The product will no longer be publicly supported after this date.

Therefore, DriverPacks support for 2000 has ended also.

Official support for XP ends 8 Apr 2014.
http://www.microsoft.com/en-us/windows/ … pport.aspx

73

(42 replies, posted in Hardware)

Well, we can try to extrapolate the HWID for the drive controller from the Sony XP drivers here:
http://esupport.sony.com/US/p/model-hom … ownloadTab

From the txtsetup.oem file

[HardwareIds.scsi.iaStor_ICH8M]
id = "PCI\VEN_8086&DEV_282A&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH8M]
id = "PCI\VEN_8086&DEV_2829&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH8R]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH8R]
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ESB2]
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ESB2]
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH7DH]
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"

[HardwareIds.scsi.iaStor_ICH7MDH]
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7R]
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7M]
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6M]
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"

A good place to start is to edit the dpms .ini file and change these two sections:

[I2]
; 7.0.0.1020
ms_count=1
ms_1_deviceName="Intel ESB/ESB2/ICH6/ICH7 SATA AHCI/RAID 7.0"
ms_1_tag="iastor2"
ms_1_sysFile="iastor2.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24D1&CC_0106,PCI\VEN_8086&DEV_2651&CC_0106,PCI\VEN_8086&DEV_2652&CC_0104,PCI\VEN_8086&DEV_2652&CC_0106,PCI\VEN_8086&DEV_2653&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

[I3]
; 7.8.0.1012
ms_count=1
ms_1_deviceName="Intel ICH8/ICH9/EP 80579 SATA AHCI/RAID Matrix 7.8"
ms_1_tag="iastor3"
ms_1_sysFile="iastor3.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2681&CC_0106,PCI\VEN_8086&DEV_2682&CC_0104,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_5029&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"


...to read...

[I2]
; 7.0.0.1020
ms_count=1
ms_1_deviceName="Intel ESB/ESB2/ICH6/ICH7 SATA AHCI/RAID 7.0"
ms_1_tag="iastor2"
ms_1_sysFile="iastor2.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24D1&CC_0106,PCI\VEN_8086&DEV_2651&CC_0106,PCI\VEN_8086&DEV_2652&CC_0104,PCI\VEN_8086&DEV_2652&CC_0106,PCI\VEN_8086&DEV_2653&CC_0106"
ms_1_isBusExtender=false
;ms_1_exc_disableIfOS="w2k"

[I3]
; 7.8.0.1012
ms_count=1
ms_1_deviceName="Intel ICH8/ICH9/EP 80579 SATA AHCI/RAID Matrix 7.8"
ms_1_tag="iastor3"
ms_1_sysFile="iastor3.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2681&CC_0106,PCI\VEN_8086&DEV_2682&CC_0104,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_5029&CC_0106"
ms_1_isBusExtender=false
;ms_1_exc_disableIfOS="w2k"

Delete the QSC folder in DriverPacks BASE, repackage the dpms archive and integrate into your source again (you can skip all the other DriverPacks for now).

74

(42 replies, posted in Hardware)

silents429 wrote:

Second I am not using XP hence the title, and it fails when it doesn't see my HDD..

Oops. Sorry.
Yes, the HWID tool needs to run on the affected machine.

75

(42 replies, posted in Hardware)

silents429 wrote:

I tried using the driverpacks and correctly put them on with the driverpack BASE.

Please post your DPs_BASE.log.
At what point in XP setup does it fail?