You are not logged in. Please login or register.
DriverPacks.net Forum » DriverPack Mass Storage » [Nightlies] DP_MassStorage_wnt5_x86-32_1304-1412 - Public
Sorry that I hurt you!
But I don't understand. The release XP DPMS has a folder structure like \D\M\I5 , the new nightly builds have a folder structure of \D\M\I\5. The old INI file had [I5], the new INI file has [I-5].
That looks like a change to me...
If you look at older mass storage files you will find lots of entries that use subfolders.
The one you used to write your program may not have but we have done that before and now.
I am sorry that you used a version that did not have sub folders in it to write your code. but that is not our fault.
I used the 'Latest DriverPacks' link on the main page which contained a link to a torrent for 'DriverPack Mass Storage 12.09 for Windows 2000/XP/2003 (x86)'. It is also featured in the 'Most downloaded' section.
It is also the most recent on in the list http://driverpacks.net/driverpacks/wind … ss-storage
Surely that is the recommended one which most people are guided to and will use?
Let me put it another way, originally we had mass storage packs with sub folders. At some point the pack became flat, with no sub folders. Now it has sub folders again. The program and features have not changed. Sub folders were always supported and still are. That has not changed.
You simply picked a version that didn't have any and so you were surprised when they reappeared.
And yes I can see that the "current version" would make sense to use.
But we didn't change anything, you simply did not pick the best example to use to write your code 
. And i am certainly not saying that is your fault either. the current version at that time simply did not demonstrate that convention.
you just needed to learn a bit more about whet is supported, since that scenario did not exist in your example you could not have known about it. But we didn't change our rules. if anything we reverted to our old style.
Also when people have issues many times we recommend that they try an older version. Some times we break things in newer versions and the older version will work when the latest greatest does not. Now there is an advantage to everyone... your code will now work with our older packs too .
OK, I was unlucky then. Is there a definition/specification for the INI file format?
It's in the FAQ section !
ahh, OK - I guess you are referring to http://forum.driverpacks.net/viewtopic.php?id=2461 ?
There is a mention of the INI and driver folder naming format a long way down. Not exactly easy to find. Anyway, I know now. cheers 
it's not an easy thing to deal with as you well know !
No easy way to keep is short and sweet.
Love your Easy 2 Boot - I use it all the time!
I am so glad you are here!
Jeff
P.S. During the development of DPMS2, I wrote a blog entry on what I had learnt about the txtsetup.oem file format at http://rmprepusb.blogspot.co.uk/2013/06 … disks.html
This may be useful to others.
That is VERY cool! thank you.
Hi
The new Easy2Boot seems to work fairly well with the new INI format now - thanks.
I was contacted by someone trying to install XP to a Intel Series 8 Z87 mainboard using DP_MassStorage_wnt5_x86-32_1403071.7z and the new Easy2Boot v1.31.
The controller is identified as 8086 8C02, but the only matching PCI ID in the INI file is for w2k3 (D\M\I\A) so the install didn't work.
He said that the INF file in D\M\I\9 was actually successfully picked up and used by XP when he pointed XP at it.So 8086 8C02 does not seem to be supported yet by this build for XP?
P.S. AsMedia 106x SATA controller PCI 1B21 0612 D\M\AS worked OK though.
all we need to do is move the matching HWID from I\A to I\9 or add the matching HWID to I\9... What is the BEST matching HWID to add (or move) ???
The I-A section is OK as it is for w2k3.
The extra PCI ID needs adding to the I-9 section 8086 8C02 1106. He is testing it tonight so I will let you know if it succeeds.
PCI\VEN_8086&DEV_8C02&SUBSYS_1106? or
PCI\VEN_8086&DEV_8C02&CC_1106 or
PCI\VEN_8086&DEV_8C02&REV_1106 or
PCI\VEN_8086&DEV_8C02
(can you please specify the exact HWID)
It will be included in section [I-9] when you confirm it works. No problem.
I used DP_MassStorage_wnt5_x86-32_1403071.7z for testing
platform = "wnt5_x86-32"
name = "MassStorage"
classes = "hdc,SCSIAdapter"
rootdir = "D\M"
; version 1403071
driverCount = 351
; number of .Inf files
; OPTIONAL
decompSize = 66728474
; compSize = unknown
; note that 'deviceName' only shows 54 chars
And modified the I-9 section to add in 8086 8C02 as follows:
[I-9]
ms_count=1
; 11.2.0.1006
ms_1_deviceName="Intel ICH7M/R-DH/8R/9M-E/10, 5/6/7/8 Series - RST 11.2"
ms_1_tag="iastor9"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_8C02&CC_0106,PCI\VEN_8086&DEV_1C02&CC_0106,PCI\VEN_8086&DEV_1C03&CC_0106,PCI\VEN_8086&DEV_1E02&CC_0106,PCI\VEN_8086&DEV_1E03&CC_0106,PCI\VEN_8086&DEV_2923&CC_0106,PCI\VEN_8086&DEV_3A03&CC_0106,PCI\VEN_8086&DEV_3A23&CC_0106,PCI\VEN_8086&DEV_27C1&CC_0106,PCI\VEN_8086&DEV_2929&CC_0106,PCI\VEN_8086&DEV_3A22&CC_0106,PCI\VEN_8086&DEV_3B22&CC_0106,PCI\VEN_8086&DEV_3B23&CC_0106,PCI\VEN_8086&DEV_3B29&CC_0106,PCI\VEN_8086&DEV_3B2F&CC_0106,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_27C6&CC_0104,PCI\VEN_8086&DEV_2822&CC_0104,PCI\VEN_8086&DEV_282A&CC_0104,PCI\VEN_8086&DEV_0816&CC_0106,PCI\VEN_8086&DEV_2323&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"
E2B worked up to the point where I could see the SATA drives on my Z87-A system - I did not test any further as I didn't want to trash my system.
Last edited by SteveSi (2014-04-01 10:41:35)
That's exactly what we need to know
It would seem that simply adding that HWID to the [I-9] section might hold some unpleasant surprises for Server2003 integrators. A final solution may be to split the section, one for XP HWID's, and the other for 2003 HWID's. That way RSTe is still available for Server2003 (supported til July 2015, BTW).
When i do my final round of testing for the RC's, i would like to test one of your solutions in addition to WinSetupFromUSB "head-to-head" with results made freely available for both camps in case improvements can be made to either or both projects. Obtaining feedback for these nighlies has been difficult, if not for the wonderful few that have been kind enough to do so. If i have to give some feedback on other projects to receive feedback on this project, i'm ready, willing and able.
What can i do to assist, and how do i get started? Your web page is kind of confusing though loaded with info.
I have little fear that software will irreparably trash any of my systems short of damaging the firmware boot block (if i'm wrong, pls point out why).
Thank you again for those previous reports, Mr. Si!
"When you're that good, they call you Mister."
Last edited by TechDud (2014-04-03 17:44:45)
Hi
Well WinsetupFromUSB has used my DPMS2 grub4dos batch file (and Ilko probably will use the new one too).
So the results will be similar (except that Easy2Boot uses an ISO file directly and so WinSetupFromUSB will probably be successful on more systems than E2B).
The new test version E2B 1.32 (on www.easy2boot.com - downloads - alternate) has some menus in the UTILITIES menu which may be useful for testing driverpack INI files on different systems without actually needing to install.
You can test in a VM by booting using DavidB's VMUB utility + VirtualBox.
Basically, the DPMS2.g4b grub4dos batch file runs chkpci (a grub4dos utility by chenall) which finds the mass storage scsi/sata/raid controller PCI ID and then find the corresponding section in the DriverPack INI file. The DPMS2.g4b batch file then parses the data from the INI file section, goes to the correct folder (e.g. \D\M\I\9) and then looks at the INF files to pull out the required entries to make a txtsetup.oem file. The files mentioned in the txtsetup.oem file plus the txtsetup.oem file are then copied from the source folder (e.g. \D\M\I\9) to a virtual floppy drive (held in memory).
Two floppy drives are created. One has a [Defaults] for the firadisk driver, the other txtsetup.oem file on the other virtual floppy drive has a [Defaults] section pointing to the correct SRS driver. In this way, XP Setup sees two floppies (virtually identical files on each) and loads the firadisk driver and the SRS driver. Later it copies the driver files from one of the floppies to the hard disk (which is why they have identical driver files on them).
A floppy file 'dir' listing and txtsetup.oem files are copied to some files when DPMS2 runs so you can examine them afterwards if you like. All this is in the \_ISO\e2b\grub\DPMS folder on the Easy2Boot USB drive.
My problem is that I am now retired and so I don't have a great selection of hardware to test anything on. When I worked for a large computer manufacturer, I had loads of systems I could test of all ages and loads of HDDs I could trash!
you don't need to split anything TD, don't confuse textmode and PNP mode they are not related at all.
putting a HWID in the INI file will not change anything related to PnP drivers
This is the as-of-yet untested modified section:
[I-9]
ms_count=2
; 11.2.0.1006
ms_1_deviceName="Intel ICH7M/R-DH/8R/9M/10, 5/6/7/8/9series - RST 11.2"
ms_1_tag="iastor9"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_1C02&CC_0106,PCI\VEN_8086&DEV_1C03&CC_0106,PCI\VEN_8086&DEV_1E02&CC_0106,PCI\VEN_8086&DEV_1E03&CC_0106,PCI\VEN_8086&DEV_2923&CC_0106,PCI\VEN_8086&DEV_3A03&CC_0106,PCI\VEN_8086&DEV_3A23&CC_0106,PCI\VEN_8086&DEV_27C1&CC_0106,PCI\VEN_8086&DEV_2929&CC_0106,PCI\VEN_8086&DEV_3A22&CC_0106,PCI\VEN_8086&DEV_3B22&CC_0106,PCI\VEN_8086&DEV_3B23&CC_0106,PCI\VEN_8086&DEV_3B29&CC_0106,PCI\VEN_8086&DEV_3B2F&CC_0106,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_27C6&CC_0104,PCI\VEN_8086&DEV_2822&CC_0104,PCI\VEN_8086&DEV_282A&CC_0104,PCI\VEN_8086&DEV_0816&CC_0106,PCI\VEN_8086&DEV_2323&CC_0106,PCI\VEN_8086&DEV_8C82&CC_0106,PCI\VEN_8086&DEV_8C83&CC_0106,PCI\VEN_8086&DEV_8C02&CC_0106,PCI\VEN_8086&DEV_8C03&CC_0106,PCI\VEN_8086&DEV_8D02&CC_0106,PCI\VEN_8086&DEV_1F22&CC_0106,PCI\VEN_8086&DEV_9C02&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,w2k3"
ms_2_deviceName="Intel 7M/R-DH/8R/9M/10, 5/6/7/8/9series - 2k3 RST 11.2"
ms_2_tag="iastor9s"
ms_2_sysFile="iastor.sys"
ms_2_hwids="PCI\VEN_8086&DEV_1C02&CC_0106,PCI\VEN_8086&DEV_1C03&CC_0106,PCI\VEN_8086&DEV_1E02&CC_0106,PCI\VEN_8086&DEV_1E03&CC_0106,PCI\VEN_8086&DEV_2923&CC_0106,PCI\VEN_8086&DEV_3A03&CC_0106,PCI\VEN_8086&DEV_3A23&CC_0106,PCI\VEN_8086&DEV_27C1&CC_0106,PCI\VEN_8086&DEV_2929&CC_0106,PCI\VEN_8086&DEV_3A22&CC_0106,PCI\VEN_8086&DEV_3B22&CC_0106,PCI\VEN_8086&DEV_3B23&CC_0106,PCI\VEN_8086&DEV_3B29&CC_0106,PCI\VEN_8086&DEV_3B2F&CC_0106,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_27C6&CC_0104,PCI\VEN_8086&DEV_2822&CC_0104,PCI\VEN_8086&DEV_282A&CC_0104,PCI\VEN_8086&DEV_0816&CC_0106,PCI\VEN_8086&DEV_2323&CC_0106,PCI\VEN_8086&DEV_8C82&CC_0106,PCI\VEN_8086&DEV_8C83&CC_0106,PCI\VEN_8086&DEV_8C03&CC_0106,PCI\VEN_8086&DEV_9C02&CC_0106"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k,wxp"PCI\VEN_8086&DEV_8C82&CC_0106 & PCI\VEN_8086&DEV_8C83&CC_0106 have been added to dps7AHCI.inf in addition, to hopefully support 9 Series.
I wonder if a wXP source with drivers integrated with DPs_BASE would be sufficient to successfully use Easy2Boot_v1.31.zip
Have had my widest success with WinSetupFromUSB using same methodology, and deselecting "use D-P-M-S.iso". Of course, that is for a flat file system.
Last edited by TechDud (2014-04-05 16:25:18)
If you had an integrated XP ISO, then you should just need to put the ISO in \_ISO\WINDOWS\XP folder and make sure that \_ISO\e2b\grub\DPMS\DriverPack.ini is present but empty so it doesn't pick any OEM DPMS driver (just firadisk).
Copy the latest driverpack to \_ISO\e2b\grub\DPMS folder (the folder \_ISO\e2b\grub\DPMS\D\M needs to be present).
If you want to test the DPMS2 feature of E2B, then rename the INI file at \_ISO\e2b\grub\DPMS to DriverPack.ini - then my DPMS2 code will create two F6 floppies, one with the Firadisk driver and the other with the SRS driver.
The other way to test an integrated ISO is to drop the ISO into \_ISO\WINDOWS\XP folder and do not have any \_ISO\e2b\grub\DPMS\DriverPack,ini file - then press F6 at XP Setup and select FiraDisk 32-bit driver and then continue install.
Thank you, sir. I will ensure any comparisons are fair and balanced, with respect to the fact that both are freeware and much volunteer person-hours (years) have gone into their respective creation. Notes will be taken to be shared at a later date, privately first - then publicly, if agreed at that time.
Last edited by TechDud (2014-04-07 19:45:20)
Wow That was VERY helpful i may put that in a FAQ at some point
Updated with Acheron's modified Marvell_Cleanup.cmd from this post, and changes from this post above (, et cetera?).
It hasn't been tested. This is just an interim Nightly.
A tested newer pack should be available before the end of next week.
DP_MassStorage_wnt5_x86-32_1404011.7z - 10.73 MB 778756E74BCB91192D20B6CD7A42878710BB97C4
* - edit: link removed - updated near last post in this topic
Note that the DP_MassStorage_IntelIDE or pciIDE pack is still used for this Nightly, as described in this post. They will be deprecated in the next Nightly, as the MassStorage pack is once-again unified.
Last edited by TechDud (2014-05-09 08:17:28)
Just wanted to say your efforts are appreciated, you can count on at least one person who's actively utilizing your updates for PE discs I use to scan friends / relatives PC's for malicious files. There's very few systems your driver pack updates won't support!
It's always nice to hear praise, it puts wind in our sails .
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.027 seconds, 10 queries executed ]