Hi,
Thanks.
Note to Jeff; it supports 2000/2003/XP.
It is an INTEL device. I'll check for issues (dupe HWIDs), but think it will end up in there.
901 2008-02-04 11:06:01
Re: [REL] Intel Turbo Memory XP dummy driver (2 replies, posted in DriverPack Chipset)
902 2008-02-03 07:51:16
Re: Just a silly post-integration question (6 replies, posted in Feedback and Support - DriverPacks Base)
I wished we could say there will never be problems with driver conflicts, but we do try to avoid conflicts when we build the DriverPacks archives.
When you look at supported device links in the overview page, you are able to tell what is in it, and then you select the packs you want.
You should also know you can modify the content of the archives and repack them with a new higher version number.
For instance, at the moment I am working on WLAN because it needs some pruning.
The current release is DP_WLAN_wnt5_x86-32_712.7z
WLAN does not have an INI..
I let 7zip unpack it .. so it created a new folder wich has the name of the PACK..
Then I renamed that folder by changing the number to a higher number.
it was still January, so that became DP_WLAN_wnt5_x86-32_801forpruning.7z
(you can see I also added forpruning, which immediately tells me this is not a released pack..)
I pruned some 72 doubles.
This pack has NO INI, so when I use 7zip, I Hit F2 on the folder, CTRL-C to copy the name of folder, and then I select the D folder to zip it up.
I CTRL-V pasted DP_WLAN_wnt5_x86-32_801forpruning.7z into the name field, and then changed 801 into 802.
Viola, I have a new WLAN I can test.
Mass storage is a special pack.
It has an INI.
when you discover that a particular driver creates a problem for you, you can edit the pack.
You use 7zip to unzip it into a folder.
Rename it, and give that new folder a higher version name
An example, 802 (year/month) becomes 8021 (year/month/revision).
And if it was 8021 to begin with it would change to 8022.
what can you do now? You can edit that INI.
When you remove INI sections and leave the folder intact, there is a high probability that everything works after you repack the INI and D folder.
BUT, when you remove a folder, you had better also edit the INI and delete the corresponding section.
If you remove D\M\D2 then you search for section [D2] in the INI.
Please delete the section if you removed the folder.
(By the way, [D2] contains that wretched LSI_SAS.EXE which is case sensitive in suprising ways.)
We fixed the issue for server 2003, but it still acts up for windows 2000? It is a SERVER 2000/2003 driver.. Can I disable it for windows 2000 and expect it to work in Server 2000?)
I will briefly mention that in Mass storage you could edit INI to disable a driver.
you could paste
ms_1_exc_disableIfOS="w2k"
at the bottom of the [D2] section.
another alternative is that you change
[D2]
ms_count=1
into
[D2]
ms_count=0
(zero disables the section, but leaves the driver intact for PnP.)
After you do the edits and/or pruning in that new mass storage folder you use 7zip to repack..
You select the D folder and INI file, and rightclick to use 7zip on selection.
It will automatically suggest the name of the folder, which was already renamed to higher version..
settings for 7zip are Ultra/LZMA/compact.
(look at RAM usage.. The new version of 7zip is not going to let you use almost two Giga while packing it up.. )Viola..
===========================
Chipset is another special case.
It has no visible INI.
BUT. A CRITICAL error can happen if you modify CHIPSET (reduce it), and it can happen whether you use QSC or not.
A few folders were hardcoded in the method one slipstream module, and if you touch the affected folders, whammo, you get a CRIT.
==================
Sound and graphics have INI as well, and the creators know how difficult these packs are.
The INI sections are ESSENTIAL to all sound and graphics drivers they was written for.
Without them, they will not properly install.
-------
when you repack you must include the edited INI.
btw, you should NEVER change the INI's name.
in 7zip, we use ULTRA compression,LZMA, and COMPACT.
I read somewhere that not using COMPACT can be an issue with repacked DriverPacks.
903 2008-02-03 07:44:22
Re: I have problem with mass storage (1 replies, posted in DriverPack Mass Storage)
hi,
welcome to DriverPacks.
the problem is a weird DELL driver in [D2]
( location D\M\D2 )
-------
Mass storage is a special pack.
It has an INI.
when you discover that a particular driver creates a problem for you, you can edit the pack.
You use 7zip to unzip it into a folder.
Rename it, and give that new folder a higher version name
An example, 802 (year/month) becomes 8021 (year/month/revision).
And if it was 8021 to begin with it would change to 8022.
what can you do now? You can edit that INI.
When you remove INI sections and leave the folder intact, there is a high probability that everything works after you repack the INI and D folder.
BUT, when you remove a folder, you had better also edit the INI and delete the corresponding section.
If you remove D\M\D2 then you search for section [D2] in the INI.
Please delete the section if you removed the folder.
(By the way, [D2] contains that wretched LSI_SAS.EXE which is case sensitive in suprising ways.)
We fixed the issue for server 2003, but it still acts up for windows 2000? It is a SERVER 2000/2003 driver.. Can I disable it for windows 2000 and expect it to work in Server 2000?)
I will briefly mention that in Mass storage you could edit INI to disable a driver.
you could paste
ms_1_exc_disableIfOS="w2k"
at the bottom of the [D2] section.
another alternative is that you change
[D2]
ms_count=1
into
[D2]
ms_count=0
(zero disables the section, but leaves the driver intact for PnP.)
After you do the edits and/or pruning in that new mass storage folder you use 7zip to repack..
You select the D folder and INI file, and rightclick to use 7zip on selection.
It will automatically suggest the name of the folder, which was already renamed to higher version..
settings for 7zip are Ultra/LZMA/compact.
(look at RAM usage.. The new version of 7zip is not going to let you use almost two Giga while packing it up.. )Hope this helps.
I will try fix this windows 2000 issue with that DELL thing I sweared at more than once.. 
904 2008-02-03 01:48:22
Re: Just a silly post-integration question (6 replies, posted in Feedback and Support - DriverPacks Base)
Hi,
welcome to DriverPacks.
I will assume you made the ISO bootable, and that would make the DISC you made from it bootable as well.
If you just want to look at how it works for you, you could install Vitual PC 2007 from Microsoft, and let it run setup from that ISO you made. (When it finishes, do not activate that install..)
But, you will want to use it on real hardware and to do that you run setup from that disc.
You made a selection of drivers BEFORE you integrated.
Windows setup will use those added drivers and should find your hardware by its own sweet self now.
905 2008-02-02 13:12:40
Re: Testers Needed (76 replies, posted in News)
Bug or feature?
RC3alpha
Ran M1, Mass storage nightly 8015 and TXTmode, on a source that had been done with an earlier Mass Storage Pack..
2008-02-02 01:58:56 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2008-02-02 01:59:36 : <CRIT> Invalid settings for D\M\S5\Si3112r driver!
I looked at the INI section [S5] of that pack. I saw nothing wrong, and then ran on a clean source.
Same error. Looked again.
in the INI, [S5] had ms_1_isBusExtender=False
The others have
ms_1_isBusExtender=false
I changed the False to false, then packed it up, and ran with this..
It got past this section, (Case sensitive about F/false?? ) and somewhat later gave me a line -1 variable used without being declared.
this log was generated when I ran it AGAIN, to read the error again.. (sorry about that.. I just re-installed snagit so I can capture output..)
2008-02-02 02:38:00 : <INIT> DriverPacks BASE 8.01.rc3alpha initialized.
2008-02-02 02:38:00 : <INIT> Host environment: WIN_XP Service Pack 2 on X86 CPU.
2008-02-02 02:38:01 : <INIT> Old temporary working directory deleted.
2008-02-02 02:38:01 : <INIT> Created temporary working directory.
2008-02-02 02:38:01 : <INIT> Imported proxy settings from Internet Explorer.
2008-02-02 02:38:01 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2008-02-02 02:38:01 : <INIT> Detected DriverPack Graphics A 8.01.2!
2008-02-02 02:38:01 : <INIT> Detected DriverPack Graphics B 8.01.2!
2008-02-02 02:38:01 : <INIT> Detected DriverPack Graphics C 8.01!
2008-02-02 02:38:01 : <INIT> Detected DriverPack LAN 8.01!
2008-02-02 02:38:01 : <INIT> Detected DriverPack MassStorage 8.01.6!
2008-02-02 02:38:01 : <INIT> Detected DriverPack MassStorage 8.01.7!
2008-02-02 02:38:01 : <INIT> Detected DriverPack Sound A 8.01!
2008-02-02 02:38:01 : <INIT> Detected DriverPack Sound B 8.01!
2008-02-02 02:38:01 : <INIT> Detected DriverPack Sound B 8.01.2!
2008-02-02 02:38:01 : <INIT> Could not detect any 3rd party DriverPacks.
2008-02-02 02:38:01 : <INIT> Finished scanning.
2008-02-02 02:38:01 : <INIT> Detected settings file "F:\_DP_RC3\DPs_BASE.ini".
2008-02-02 02:38:01 : <INIT> Windows XP Professional - SP2 detected.
2008-02-02 02:38:01 : <INIT> The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2008-02-02 02:38:01 : <INIT> Imported settings from settings file.
2008-02-02 02:38:01 : <GUI> Initialized GUI.
2008-02-02 02:38:01 : <GUI> Created a list of all available language files.
2008-02-02 02:38:02 : <GUI> Set the last used language, English, as the GUI language.
2008-02-02 02:38:04 : <GUI> Saved settings!
2008-02-02 02:38:04 : <GUI> Closed GUI.
2008-02-02 02:38:04 : <SEL> Selected module: mod_slip_wxp_x86-32_disc_m1.
2008-02-02 02:38:04 : <PREP> QuickStream Cache available for DriverPack MassStorage text mode drivers!
2008-02-02 02:38:07 : <PREP> Removed all attributes from \I386.
2008-02-02 02:38:09 : <PREP> Deleted old method 1 related files.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver DPTI2O.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver adpu160m.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver ALIIDE.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver mraid35x.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver dac2w2k.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver dac960nt.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver ultra.sys.
2008-02-02 02:38:09 : <PREP> Restored original mass storage text mode driver ql12160.sys.
2008-02-02 02:38:09 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2008-02-02 02:38:09 : <PREP> Restored \I386\winnt.sif.
2008-02-02 02:38:09 : <PREP> Restored \I386\txtsetup.sif.
2008-02-02 02:38:09 : <PREP> Restored \I386\dosnet.inf.
2008-02-02 02:38:10 : <SLIP> Processing the files now. This may take a minute.
2008-02-02 02:38:11 : <SLIP> Slipstreamed DP MassStorage text mode drivers using QuickStream Cache.
2008-02-02 02:38:18 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2008-02-02 02:38:18 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2008-02-02 02:39:02 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2008-02-02 02:39:02 : <SLIP> QuickStream Cache available for DriverPack MassStorage!
2008-02-02 02:39:09 : <SLIP> Slipstreamed DriverPack MassStorage using the QuickStream Cache.
2008-02-02 02:39:09 : <SLIP> No DP Graphics packs were selected KB883667 will not be added
2008-02-02 02:39:10 : <SLIP> Extracted bin\DPsFnshr.7z to \$OEM$\$1.
2008-02-02 02:39:10 : <SLIP> Created OemPnpDriversPath entry. The length is 1000, which does not exceed the 4096 characters limit.
2008-02-02 02:39:10 : <SLIP> Added OemPnpDriversPath entry to \I386\winnt.sif.
I will look at path.
EDIT; winntsif was processsed, and Mass storage path was there.
906 2008-02-02 09:39:57
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
Hi,
OverFlow discovered something which can explain your problem.
He discovered that when you use a different mass storage pack and do a second run on a source, that the cleanup gets done using the INI file from the new pack.
When the new pack has differences in the exceptions and filenames, some earlier drivers were not cleaned up?
He has a fix in the new DPsBase RC3 alpha..
I think he saw that by investigating the code, and I also think nobody ever bothered to look (I never compared a clean slipstream with a build that was done a second time with a new pack.)
Point is, I usually test slipstream on clean copy from source.
I sometimes do a second run on same source using a different method, but then I am (most often) using same packs.
I do not know how other experienced testers test, but can see how this could stay undetected for so long.
907 2008-02-01 20:34:53
Re: Testers Needed (76 replies, posted in News)
OverFlow wrote:
fixed unreported problem,
if base detects that it was run on a source before it will back out of all of its changes and restore original files.
currently the mass storage ini from the most current pack is used to restore original files from a previous slipstream of base.
if the list of skipped or replaced drivers changed then it would be possable that not all files would be restored.
Now we copy mass ini to i386 when adding textmode drivers then use that mass INI for restoreing original files before slipstreaming the current selections. this way the same list is used to reset / restore as was used to install.Misc code cleanup...
jeff
This could possibly explain why it worked for this tester and not for another when we read reports about some testpacks? Sometimes the testpack used renamed files, or different tagnames, or different sections were marked for skip. You can bet I will try look for signs of this now that I was made aware this could happen.
908 2008-02-01 09:53:08
Re: Can't find LAN driver (3 replies, posted in DriverPack LAN)
Q9: Why don't I find RTL8201x driver on the website?
A9:
RTL8201, RTL8201BL, RTL8201CL, RTL8201CP, RTL8201N and RTL8211B(L) are all PHYceiver. That is a driverless hardware device. Software driver are relative to Network controller ( MAC ) which is integrated into chipset in such case mostly. Please contact your mother board maker or chipset manufacturer to obtain proper driver support.
909 2008-01-31 10:37:23
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
Hi
we have a Russian helpers in the team, and I will suggest you watch your language.
910 2008-01-30 12:38:58
Re: [REQ] MassStorage 7.12 not Detecting SATA Harddisk (51 replies, posted in DriverPack Mass Storage)
uploading it again.. using same name 8016
you won't believe this.
I had uploaded from a folder in which I had forgotten to copy the new L1 folder... which breaks streaming.
it should be up again..
911 2008-01-30 12:34:21
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
uploading it again..
you won't believe this.
I had uploaded from a folder in which I had forgotten to copy the new L1 folder... which breaks streaming.
it should be up again..
912 2008-01-30 12:10:00
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
new testfile
DP_MassStorage_wnt5_x86-32_8016.7z
\L1 added INTEL (lsi) megaIDE
updated \M marvel (with driver from Intel)
mode tags in S4 and S5
moved [V] to original position in INI (V3 was and is still disabled for TXTmode.)
913 2008-01-30 07:43:24
Re: Help create .ini file to install my SAMSUNG Monitor (6 replies, posted in 3rd Party DriverPacks)
Hi,
I downloaded that CAB and used uni-extract to get the ICM, the INF and the CAT extracted.
After that, it should be as simple as rightclick the INF, and install.
EDIT, I see.. that was not your problem..
914 2008-01-30 04:19:39
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
Hi
FAIK, it is like this..
If you did not have any RAID array, then you can switch without problems.
If your hard disk is not seen, then it cannot get messed up, and the worst that can happen is that you have to re-install the driver from within safe mode..
Suppose you have a RAID array, and set the BIOS to Base mode and restart, then it won't be able to use the array. You will simply not see it.
To use a member Hard disks in Base mode, you have to use the RAID utility in BIOS to reset hard disks to NON-RAID which will WARN you that all data is going to be lost.
The other way? Suppose you add a second hard disk and want to create an array, then it will warn you that all data gets lost when you tell it you want to build the array.
915 2008-01-30 02:19:57
Re: [REQ] MassStorage 7.12 not Detecting SATA Harddisk (51 replies, posted in DriverPack Mass Storage)
new testfile
http://dev.driverpacks.thesneaky.com/dr … 32_8016.7z
\L1 added INTEL (lsi) megaIDE
updated \M marvel (with driver from Intel)
moved [V] to original position in INI (V3 was and is still disabled for TXTmode.)
916 2008-01-29 12:23:13
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
Hi
I have not made one for this..
Somebody ought to make a new Mass storage pack for that megaIDE request, but at the moment I am again working on WLAN.. I want to try finish work I started December 14, and what was stopped on December 17..
I just spent another seven hours on that pack.
(Jeff calls it grooming... The work done so far resulted in 71 removed folders.. And that should help M1 and people who hate duplicates.)
We had a test version with "mode tags" during those weeks in which I built at least 20 versions..
The mode tags could help in TXTmode.. Which is why I posted these two INI sections.
Anybody who wants can shuffle sections around in INI, or delete sections in INI.. and if he is good enough he can create new sections too... A good TXT was written by Ruudboek, and if you look for keyword "learning pains" you ought to find it.
917 2008-01-29 07:34:59
Re: Acer Aspire 5720z (14 replies, posted in Feedback and Support - DriverPacks Base)
Hi
a spare hard disk is the safest option..
When you mess up Vista's bootloader and the hidden partition, you are indeed in trouble.
918 2008-01-29 04:51:40
Re: Mini MassStorage Pack creation - seeking help (6 replies, posted in DriverPack Mass Storage)
When you repacked, did you include the edited INI?
By the way, you should NEVER change the INI's name.
In 7zip, we use ULTRA compression, LZMA, 256 wordlength and COMPACT.
I read somewhere that not using COMPACT can be an issue with repacked DriverPacks.
Oh...
let's write about how I edit mass.
I let 7zip unpack it .. so it creates a new folder wich has the name of the PACK..
Then I rename that folder by changing the last number to a higher number.
An example, 801 (year/month) becomes 8011 (year/month/revision).
And if it was 8011 to begin with it would change to 8012.
After that you do the edits and pruning in that new folder.
And then you select the D folder and INI file, and rightclick to use 7zip on selection.
It will automatically suggest the name of the folder, which was already renamed to higher version..
Ultra/LZMA/256/compact.
(look at RAM usage.. The new version of 7zip is not going to let you use almost two Giga while packing it up.. )Viola..
919 2008-01-29 04:41:48
Re: [BSOD] 0x0000007B Error with MassStorage 7.12 (Si3112r, ATI SB450) (125 replies, posted in DriverPack Mass Storage)
Hi
since we did not use MODE tags, this is expected.
I had to make a choice in the load order, and assumed RAID mode would be default in most machines.
You can change the controller mode settings in BIOS..
Or, you can unpack Mass storage, and move the [S4] section below [S5] section
And then repack mass storage along with the changed INI.
OR, you can replace the two sections with this (they are MODE tagged), and test this.
(I would be most interested to find out about THIS one...)
Now... If this will not work, and you do not want to change the BIOS setting, then we have to teach the users that they can move INI sections.
These are the mode tagged sections you could try
[S4]
ms_count=1
ms_1_deviceName="SILICON IMAGE 3112 SATALINK"
ms_1_tag="SI3112"
ms_1_sysFile="SI3112.SYS"
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_31121095&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_34238086&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_311215D9&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_B0021458&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_01661028&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_82141033&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_81E8104D&CC_0101,PCI\VEN_1095&DEV_3112&SUBSYS_82641033&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_35121095&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_01661028&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_82641033&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_35121014&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_02B71014&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_B0021458&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_820B104D&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_145A1462&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_001F6409&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_35121A5F&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_000E182D&CC_0101,PCI\VEN_1095&DEV_3512&SUBSYS_3512131F&CC_0101,PCI\VEN_1002&DEV_436E&SUBSYS_B0021458&CC_0101"
ms_1_isBusExtender=false
[S5]
ms_count=1
ms_1_deviceName="Silicon Image 3112 SATARaid Controller"
ms_1_tag="3112Rx47"
ms_1_sysFile="Si3112r.sys"
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_61121095&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_611215D9&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_34228086&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_B0031458&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0111019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0121019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0131019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0141019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A0151019&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1014147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_100B147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1402147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1404147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1802147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1804147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_1C00147B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_5930107D&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_249510F1&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_809D1043&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0270A0A0&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_044DA0A0&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_044CA0A0&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_92011905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_92151905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_904C1905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_904B1905&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A41810FD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A41910FD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_A71910FD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_90171695&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_C2001297&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_C2011297&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_15D40035&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_340217F2&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_100415BD&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_F641270F&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C0F105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C13105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C58105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C40105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C41105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C42105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C43105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C44105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C22105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_0C2A105B&CC_0104,PCI\VEN_1095&DEV_3112&SUBSYS_2A1E103C&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_65121095&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_B0031458&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1014147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1021147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_100B147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C06147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C00147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C03147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1C04147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1406147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_1407147B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_90191695&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_C2021297&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_C2031297&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_C2041297&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_534D108E&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_02C51095&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_2A1E103C&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_0C22105B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_0C2A105B&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_91451462&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_006C1025&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_010D1025&CC_0104,PCI\VEN_1095&DEV_3512&SUBSYS_0010182D&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_436E1002&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_A43110FD&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_F3631297&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_07201462&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_B0031458&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_92691509&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_5005148C&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_0A44174B&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_0A45174B&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_00301462&CC_0104,PCI\VEN_1002&DEV_436E&SUBSYS_100516F3&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_43791002&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_437A1002&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_3009103C&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_3009103C&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_207717C0&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_207717C0&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_2A20103C&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_2A20103C&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_92761509&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_92761509&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_92771509&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_92771509&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_3005148C&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_3005148C&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_71241462&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_71241462&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_81541043&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_81541043&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_816F1043&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_816F1043&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_21811071&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_21811071&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_12CB10CF&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_12CC10CF&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_1B341019&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_1B341019&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_1B351019&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_1B351019&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_71411462&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_71411462&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A54174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A54174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A55174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A55174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A56174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A56174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A58174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A58174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_3003148C&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_3003148C&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_3004148C&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_3004148C&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A62174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A62174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_43791849&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_437A1849&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_D0081631&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_D0081631&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_B0031458&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_B0031458&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_007D1025&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_007D1025&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A64174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A64174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A65174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A65174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A69174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A69174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A70174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A70174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A71174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A71174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A72174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A72174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0A73174B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0A73174B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_01311071&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_01311071&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_819B1043&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_819B1043&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_21311019&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_21311019&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_21371019&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_21371019&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_21361019&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_21361019&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_21121019&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_21121019&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_005C17C0&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_005C17C0&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_D6008086&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_D6008086&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_311015BD&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_311015BD&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_10A41734&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_10A41734&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0C81105B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0C81105B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_72421462&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_72421462&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_72541462&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_72541462&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0C83105B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0C83105B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_D6018086&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_D6018086&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_D6028086&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_D6028086&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_71731462&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_71731462&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_80091854&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_80091854&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_1033833B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_1033833B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_88241033&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_88241033&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_833B1033&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_833B1033&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_6047107B&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_6047107B&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0566A0A0&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0566A0A0&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0614A0A0&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0614A0A0&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_0611A0A0&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_0611A0A0&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_60081695&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_60081695&CC_0104,PCI\VEN_1002&DEV_4379&SUBSYS_60091695&CC_0104,PCI\VEN_1002&DEV_437A&SUBSYS_60091695&CC_0104"
ms_1_isBusExtender=false920 2008-01-27 19:59:03
Re: Testers Needed (76 replies, posted in News)
you also tested chips 801c?
I did, and did one of my eXperimental chips.
we are not yet decided..
Jeff mostly splitted.. I mostly merged. We are probably going to have a maintainable chips with INI so that we get a M1 txtmode sort of chipset install (like M1 on steroids and short path.)
EDIT; added [mostly] where needed.. we gonna discuss this anyhow.
921 2008-01-27 19:34:56
Re: Testers Needed (76 replies, posted in News)
yes.
I have txtmode OK on two wildly different machines, and a full setup was made possible by putting a LL'd drive of mine in a client's case..
By the way, that guy has a problem..
His medion from 2005 has all PQI files on HDD2
But he no longer has the recovery (retting?) exe.
After tests, the supplied DVD were used, and do not install the OEM recovery tools.
(Nice set of monitor files in there..)
want a side note? 
DriverPacks DVD worked better than medion 'windows only" re-install.
922 2008-01-27 19:19:39
Re: REQ One Driver to be included in the DP Monitor (2 replies, posted in 3rd Party DriverPacks)
thanks.
I wonder who'll do it.
I cannot.
^^bump...^^
923 2008-01-27 18:23:11
Re: Raid - Using MassStorage Driver (16 replies, posted in DriverPack Mass Storage)
from memory? 590 will fight either 520/540/630 and maybe also Nforce4
I have to look up why.
We have no easy solution to that one, and a I am Not going to write an SFx_Mini_pack.
The suggested solution is that all Nvidia with a number are edited out of INI and you leave N-TM in the INI.
you do NOT delete drivers from pack.
repack
We think 590 cannot co-exist in txtmode
I think we left it as a non-referenced folder for PnP .
You are smart, help us.
Make it work, and tell us how.
EDIT EITHER° WAS ADDED IN FIRST LINE.
924 2008-01-27 16:55:21
Re: Universal VESA/VBE Video Display Driver (5 replies, posted in DriverPack Graphics)
Hi, Faik, EGA and CGA are supported in BIOS, and XP/NT5x TXTmode still supports 460 by 600 as lowest resolution during TxTmode.
600 by 800 is lowest in VGA in XP.
VESA supports enhanced EGA/VGA/SVGA at 600/800 to 728/1024 in win3.1?
If I am wrong about TxTmode lowest, shoot.
(edit; I am not sure mobile BIOS do CGA.. Modern systems could all be minimum EGA/VGA at BIOS level. But VESA was already supporting SVGA.. with EGA as a common in BIOS..)
QUIZ..
Cga is ? bit
Ega is ? bit
VGa is ? bit
SVGA is ? bit?
what is true 32 bit?
and what cards use 64 bit?
925 2008-01-27 16:40:23
Re: windows longhorn (1 replies, posted in Software)
Hi,
welcome to DriverPacks.
We do not do "longhorn".