Jump to content

Bâshrat the Sneaky

Member
  • Posts

    5,580
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Belgium

Everything posted by Bâshrat the Sneaky

  1. Could you please send me (or attach) the IBM ATI Mobility INF file? I'll add those entries then...
  2. MANY have reported me that this works... None of the steps you described (the ones you quoted the code from) works for you?
  3. As you guys may know, I'm switching to this method for DriverPack MassStorage. So I'm re-reading the entire topic to get a clear view on it. And I *think* that we can simplify the structure. Can anyone try this: [quote]everything to: * $OEM$\TEXTMODE\ * I386\$OEM$\ .cpl, .dll, .exe, .vxd to * $OEM$\$$\OemDir\ Now I'm guessing... wouldn't this be possible:[/quote][quote]everything to: * I386\$OEM$\TEXTMODE\ * I386\$OEM$\ .cpl, .dll, .exe, .vxd to * I386\$OEM$\$$\OemDir\[/quote] Just wondering... I think this would be better for the clarity of this method, *IF* this would work. I'll try to test it tomorrow. BTW: finally stickied it... beat me for doin' that so late... EDIT: woohooow found some confirmations: - that I386\$OEM$\TEXTMODE\ should work [url="http://support.microsoft.com/default.aspx?scid=kb;en-us;816299"]source[/url] (win 2k3) and [url="http://support.microsoft.com/kb/288344/EN-US/"]source 2[/url] (win2k) AND - that I386\$OEM$\$$\OemDir\ should work and that you WON'T need I386\$OEM$ [url="http://support.microsoft.com/kb/275334/EN-US/"]source[/url] other useful link: [url="http://www.microsoft.com/technet/archive/winntas/deploy/depopt/gdautset.mspx"]http://www.microsoft.com/technet/archive/w...t/gdautset.mspx[/url] EDIT: according to this [url="http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prbc_cai_qcxl.asp"]article[/url], you don't have to include the .cat files! [quote]Catalog files (.cat) are not used during text-mode setup.[/quote]But, according to that same article, you have to use $OEM$\TEXTMODE, not I386\$OEM$\TEXTMODE... Note that this article is written specific for Windows XP, while the other ones were for win2k and win2k3... EDIT: and I've found a possible cause for the setup is restarting bug... [quote]When you are installing Microsoft Windows XP or Microsoft Windows Server 2003 on a new computer or on a computer that has the latest SCSI or IDE controller technology, you may have to use an OEM device driver to support, for example, a new mass storage controller, to continue with the installation. The symptoms that you have to install an OEM device driver include the following: The computer may keep restarting and never start the GUI installation after the text mode Setup is finished.[/quote] [url="http://support.microsoft.com/kb/310994"]source[/url]
  4. BTW... I'm rebuilding DriverPack MassStorage with the txtsetup.oem method. Will you still have to edit the dosnet.inf file then? (the txtsetup.sif file won't have to be edited!)
  5. Can you give me a link to the right page on their website (www.ali.com.tw)? Because I can't find it... Really sucky AND slow site...
  6. I don't know much (in fact almost nothing) about WinPE. I just know you have to add entries to the dosnet.inf, because several people told me that... I'm sorry, but you'll have to find some guide or someone with more experience on WinPE issues
  7. Please repeat your question in the DriverPack WLAN topic. You've posted in the wrong one Else everything becomes a mess in here...
  8. Please unzip the two inf files attached and try those. If they don't work, nothing will work!
  9. K thx... comparing now... EDIT it seems he just added support for even MORE cards than patje's tool... But according to some research I did on the net, omega's don't work, while patje's does work... Anyway, here are the ones he added: ;Extra support added for the following cards by Omegadrive: "MEDION RADEON 9600 TX (Omega 2.6.05a)" = ati2mtag_R300, PCI\VEN_1002&DEV_4E46&SUBSYS_84861787 "MEDION RADEON 9600 TX (Omega 2.6.05a) " = ati2mtag_R300, PCI\VEN_1002&DEV_4E46&SUBSYS_84841787 "MEDION RADEON 9600 TX Secondary (Omega 2.6.05a)" = ati2mtag_R300, PCI\VEN_1002&DEV_4E66&SUBSYS_84871787 "MEDION RADEON 9600 TX Secondary (Omega 2.6.05a) " = ati2mtag_R300, PCI\VEN_1002&DEV_4E66&SUBSYS_84851787 "RADEON 9800 XT (Omega 2.6.05a) " = ati2mtag_R360, PCI\VEN_1002&DEV_414A "RADEON 9800 XT - Secondary (Omega 2.6.05a) " = ati2mtag_R360, PCI\VEN_1002&DEV_416A "ATI MOBILITY FIRE GL 7800 (Omega 2.6.05a)" = ati2mtag_M7, PCI\VEN_1002&DEV_4C58 "ATI MOBILITY FIRE GL 9000 (Omega 2.6.05a)" = ati2mtag_M9, PCI\VEN_1002&DEV_4C64 "ATI MOBILITY FIRE GL T2/T2e (Omega 2.6.05a)" = ati2mtag_M10GL, PCI\VEN_1002&DEV_4E54 "ATI MOBILITY FireGL V3100 (Omega 2.6.05a)" = ati2mtag_M22GL, PCI\VEN_1002&DEV_5464 "ATI MOBILITY FireGL V3200 (Omega 2.6.05a)" = ati2mtag_M24GL, PCI\VEN_1002&DEV_3154 "ATI MOBILITY FireGL V7100 (Omega 2.6.05a)" = ati2mtag_M28GL, PCI\VEN_1002&DEV_5D49 "ATI MOBILITY RADEON (Omega 2.6.05a)" = ati2mtag_M6, PCI\VEN_1002&DEV_4C59 "ATI MOBILITY RADEON 7500 (Omega 2.6.05a)" = ati2mtag_M7, PCI\VEN_1002&DEV_4C57 "ATI MOBILITY RADEON 9000 (Omega 2.6.05a)" = ati2mtag_M9, PCI\VEN_1002&DEV_4C66 "ATI MOBILITY RADEON 9200 (Omega 2.6.05a)" = ati2mtag_M9Plus, PCI\VEN_1002&DEV_5C63 "ATI MOBILITY RADEON 9200 (Omega 2.6.05a) " = ati2mtag_M9Plus, PCI\VEN_1002&DEV_5C61 "ATI MOBILITY RADEON 9200 IGP (Omega 2.6.05a)" = ati2mtag_RS350M, PCI\VEN_1002&DEV_7835 "ATI MOBILITY RADEON 9500 (Omega 2.6.05a)" = ati2mtag_M10, PCI\VEN_1002&DEV_4E52 "ATI MOBILITY RADEON 9600/9700 Series (Omega 2.6.05a)" = ati2mtag_M10, PCI\VEN_1002&DEV_4E50 "ATI MOBILITY RADEON 9800 (Omega 2.6.05a)" = ati2mtag_M18, PCI\VEN_1002&DEV_4A4E "ATI MOBILITY RADEON X300 (Omega 2.6.05a)" = ati2mtag_M22, PCI\VEN_1002&DEV_5460 "ATI MOBILITY RADEON X600 (Omega 2.6.05a)" = ati2mtag_M24, PCI\VEN_1002&DEV_3150 "M28 (Omega 2.6.05a)" = ati2mtag_M28, PCI\VEN_1002&DEV_5D48 as well as support for FireGL cards: ;FireGL Support added for the following cards by Omegadrive: "ATI FireGL 8800 (Omega 2.6.05a)" = ati2mtag_R200GL, PCI\VEN_1002&DEV_5148 "ATI FireGL D1100 (Omega 2.6.05a)" = ati2mtag_RV370GL, PCI\VEN_1002&DEV_5B65 "ATI FireGL D1100 Secondary (Omega 2.6.05a)" = ati2mtag_RV370GL, PCI\VEN_1002&DEV_5B75 "ATI FireGL T2 (Omega 2.6.05a)" = ati2mtag_RV350GL, PCI\VEN_1002&DEV_4154 "ATI FireGL T2 Secondary (Omega 2.6.05a)" = ati2mtag_RV350GL, PCI\VEN_1002&DEV_4174 "ATI FireGL V3100 (Omega 2.6.05a)" = ati2mtag_RV370GL, PCI\VEN_1002&DEV_5B64 "ATI FireGL V3100 Secondary (Omega 2.6.05a)" = ati2mtag_RV370GL, PCI\VEN_1002&DEV_5B74 "ATI FireGL V3200 (Omega 2.6.05a)" = ati2mtag_RV380GL, PCI\VEN_1002&DEV_3E54 "ATI FireGL V3200 Secondary (Omega 2.6.05a)" = ati2mtag_RV380GL, PCI\VEN_1002&DEV_3E74 "ATI FireGL V5100 (Omega 2.6.05a)" = ati2mtag_R423GL, PCI\VEN_1002&DEV_5552 "ATI FireGL V5100 Secondary (Omega 2.6.05a)" = ati2mtag_R423GL, PCI\VEN_1002&DEV_5572 "ATI FireGL V7100 (Omega 2.6.05a)" = ati2mtag_R423GL, PCI\VEN_1002&DEV_5554 "ATI FireGL V7100 Secondary (Omega 2.6.05a)" = ati2mtag_R423GL, PCI\VEN_1002&DEV_5574 "ATI FireGL V7200 (Omega 2.6.05a)" = ati2mtag_R423GL, PCI\VEN_1002&DEV_5551 "ATI FireGL V7200 Secondary (Omega 2.6.05a)" = ati2mtag_R423GL, PCI\VEN_1002&DEV_5571 "ATI FireGL X1 (Omega 2.6.05a)" = ati2mtag_R300GL, PCI\VEN_1002&DEV_4E47 "ATI FireGL X1 Secondary (Omega 2.6.05a)" = ati2mtag_R300GL, PCI\VEN_1002&DEV_4E67 "ATI FireGL X2-256/X2-256t (Omega 2.6.05a)" = ati2mtag_R350GL, PCI\VEN_1002&DEV_4E4B "ATI FireGL X2-256/X2-256t Secondary (Omega 2.6.05a)" = ati2mtag_R350GL, PCI\VEN_1002&DEV_4E6B "ATI FireGL X3-256 (Omega 2.6.05a)" = ati2mtag_R420GL, PCI\VEN_1002&DEV_4A4D "ATI FireGL X3-256 Secondary (Omega 2.6.05a)" = ati2mtag_R420GL, PCI\VEN_1002&DEV_4A6D "ATI FireGL Z1 (Omega 2.6.05a)" = ati2mtag_R300GL, PCI\VEN_1002&DEV_4147 "ATI FireGL Z1 Secondary (Omega 2.6.05a)" = ati2mtag_R300GL, PCI\VEN_1002&DEV_4167 Try adding the following code in the driver's inf file, replacing all the old entries and tell me if it works then!
  10. hmm... you're defintely the first one! Did you use RyanVM's updatepack? If yes, which version?
  11. I can't get the Omega's extracted :s Anyone? (no, I won't install them...)
  12. DriverPack Sound V5.02 is complete! Won't be released untill the others are updated as well... changelog: V5.02 -Updated: Creative SB Audigy 1/Audigy 2/Live! from 06/23/2004, 5.12.01.0444 [1.84.50] to 10/18/2004, 5.12.02.0444 [1.84.55] -Updated: Realtek AC'97 (ALC-101/201/202/203/250/650/655/658/850) from 12/22/2004,5.10.00.5770 [3.68] to 01/28/2005,5.10.00.5780 [3.69] -Updated: Realtek HD Audio (ALC-880) from 12/22/2004,5.10.00.5770 [1.06] to 01/27/2005, 5.10.0.5116 [1.15] -Updated: VIA Vinyl from 09/01/2004,6.14.01.4070 [5.70d] to 11/01/2004,6.14.01.4080 [5.80c]
  13. Well... then I honestly don't know... I'll download the Omega's and compare with those. Do you get any specific error? An error code? A link 'Click here for details'?
  14. hmm.... does the name of your device show up on the screen? EDIT: I mean the CORRECT name...
  15. WTF... Are you installing with the INSTALLER??? Cause then it won't work... As noted in the batch file... Only the drivers themselves are modded!
  16. Finished DriverPack WLAN V5.02! Won't be released untill the others are complete. changelog: V5.02 -New: support for SAFECOM -Fixed: Atheros driver was missing
  17. The bold part is what's in the inf file, so it should work... Could you try again with this one? (supposing you're using WinXP)
  18. Update for V5.02 is complete... but won't be released until all other updates are finished... (to do: Sound & MassStorage) Changelog: V5.02 -New: added support for all SMC NICs -New: added support for Netgear FA330, FA331 NICs -New: added nVidia nForce NAM (Network Access Manager), which dramatically increased the size of DriverPack LAN! -Updated: nVidia nForce ethernet from 05/17/2004, 4.4.2 to 01/13/2005, 4.6.8 -Updated: Broadcom 57xx, 58xx, 59xx driver from 06/19/2004,7.80.0.0 to 08/23/2004,7.86.0.0 -Updated: Broadcom 440x driver from 10/31/2003, 4.23.0.0 to 11/01/2004, 4.28.0.0 -Updated: Intel drivers from 06/22/2004,8.0.11.0 & 06/22/2004,8.0.57.0 [9.0] to 10/14/2004,8.0.15.0 & 11/22/2004,8.4.21.0 & 11/04/2004,2.1.5.0 [9.2] -Updated: VIA VT6107, VT8231, VT8233, VT8235, VT8237 driver from 04/09/2004,3.32.0.0417 to 12/04/2004,3.41.0.0426 -Updated: VIA Velocity VT6120, VT6122 driver from 04/14/2004, 1.29.0.0087 to 08/03/2004, 1.34.0.0092 -Removed: duplicate VIA drivers
  19. Could you get the pci DeviceID for me? Maybe it's not included...
  20. hmm.... Doesn't it work even when you try to install it manually?
  21. And I've added support Matrox, SiS, VIA, XGI so I guess we're close to 99.99%
  22. @mociloc & iSmart: thanks!
  23. You will have to add the correct entries to your dosnet.inf. Just read the installation instructions included...
  24. You can use my mini-program that I just finished It works perfect! But it only works with the latest version... Extract to default path and then run the .cmd file from anywhere! EDIT: please rename the extension from .xyz to .exe: it's an SFX archive, but .exe wasn't allowed... EDIT2: some short explanation: it makes 2 new inf files (one for win 2K, one for win XP), with ONLY the Mobility PCI DeviceID's in it. Of course the WHQL signing is broken for these two files, but the original ones are still WHQL signed.
  25. Hmm... How can this happen? Those drivers ARE signed and probably they're newer... So they should get installed... What's the version of the driver that ships with Windows?
×
×
  • Create New...