Helmi wrote:
jtdoom wrote:

I was told (by experts) most home routers have a DMZ which is not really a DMZ.

That's true.
However, how many home users (not counting any of you (semi-)pros here, obviously) will make use of that feature?
For the ususal guy, port forwarding will do.
Of course, then there's a certain risk with this one port, but if you want total security, unplug from the net neutral

Agreed.

For my home network, I use a Linksys 802.11b (old, but reliable) router for wired/wireless connectivity and Symantec Client Security 3.1.6 (corporate SAV + soft-firewall).
The router (with IP stealthing/masking) takes care of shielding my machines from all but the determined idiots out there.  The PFW protects my machines from each other in the event one PC gets compromised from behind the router (within the network).
It's a good setup that's saved me at least once.

Mr. Dub wrote:

I have SAV install itself during runoncexec... and by the time it gets around to doing the driverpacks finisher, SAV has already updated itself with the latest defs and then catches the driverpack files with it's auto-protect feature.

I also install SCS 3.1.6 during ROE and SAV has NEVER reported a virus before/during/after install/logon or anytime for that matter.  My SCS installer has the (5/30) vdef updates integrated and doesn't need to update from the internet after install.
My guess is the problem is on your end.  Scan your sources before building your ISO (something I need to get into the habit of doing myself smile )

That's not the only item that got screwed up in the tracker.
I can't fix it at the moment, hopefully one of the main team can sort it out in the next couple of hours.

The tracker somehow got reverted to an older one when jtdoom updated the LAN DP to 7.06.
Also, some of the newer DriverPacks themselves got dropped from the ftp server in favor of older releases.

I have a gut feeling that someone "synced" their local folder over the top of the ftp server and overwrote the files.

3,853

(3 replies, posted in News)

I just logged into the ftp site, the LAN 7.06 is not there.
It'll get fixed this morning.  Jtdoom updated really late last night/morning.

mr_smartepants wrote:

$10 says ATI releases Catalyst 7.6 five minutes after we release. tongue

Well at least they got 7.5 out the door on the last day of the month. yikes
http://ati.amd.com/support/drivers/xp/radeonx-xp.html

lieblingsbesuch wrote:

The new Catalyst will have Steam integrated. Not so good, eh?

Oh God!  Unfortunately, you're right.  sad
The 7.5 installer lists "Free Games Offer" and "Earthsim" as default options.
Well, you can bet that crapware wont make it into the DriverPacks! smile

Yes, be patient.  New DP Graphics_A 7.05.3 is in testing now. 
Looking good so far.  smile

$10 says ATI releases Catalyst 7.6 five minutes after we release. tongue

3,856

(2 replies, posted in Feedback and Support - DriverPacks Base)

Yes, the DPbase will integrate drivers into your Windows source, allowing you to create a bootable Windows install disk that will support almost all modern hardware with up-to-date drivers.

You can follow our walkthrough tutorial at:
http://forum.driverpacks.net/viewtopic.php?id=1449

More basic info is available on the main page:
http://www.driverpacks.net/DriverPacks/

Welcome to DriverPacks!
smile

3,857

(9 replies, posted in News)

Edit*
post deleted.

3,858

(9 replies, posted in News)

Helmi wrote:

So the 7.05.2 on the server is really just a 7.04 in disguise now or what?

Ummm....Yeah.

Helmi wrote:

Just asking because I am about to create a new disc and want to know whether I should use that or rather hold out a little for a fixed version wink

I'm working on it.  sad

3,859

(9 replies, posted in News)

The DP_Graphics_A_wnt5_x86-32_705 INI still has the errors I reported in this thread.
And, the initial INI entries don't match...703 nightly? smile

[DriverPack]
platform	= "wnt5_x86-32"
name		= "Graphics A"
; version 703 nightly
rootDir		= "D\G"
; OPTIONAL
classes		= "Display"
driverCount	= 4
decompSize	= 322
compSize	= 67.65


[A-1]
; REQUIRED
exc_count		= 2
; OPTIONAL
exc_1_tagFiles	= 2
exc_1_tagFile1	= "%SystemDrive%\ATICCC.ins"
exc_1_tagFile2	= "%DPSROOT%\D\G\A\1\ATICCC.exe"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 4
exc_1_command1    = "%DPSROOT%\D\G\A\1\ATICCC.exe -y -o%DPSTMP%"
exc_1_command2    = "msiexec /i %DPSTMP%\ISScript9.Msi /qn /norestart"
exc_1_command3    = "msiexec /i %DPSTMP%\ATICCC.msi /qn /norestart"
exc_1_command4    = "cmd.exe /c rd /s /q %DPSTMP%"
exc_2_tagFiles	= 2
exc_2_tagFile1	= "%SystemDrive%\ATICCP.ins"
exc_2_tagFile2	= "%DPSROOT%\D\G\A\1\ATICCP.exe"
exc_2_+hwids	= 0
exc_2_-hwids	= 0
exc_2_+infFiles	= 1
exc_2_+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
exc_2_-infFiles	= 0
exc_2_commands	= 3
exc_2_command1	= "%DPSROOT%\D\G\A\1\ATICCP.exe -y -o%DPSTMP%"
exc_2_command2	= "%DPSTMP%\Setup.exe /K"
exc_2_command3	= "cmd.exe /c rd /s /q %DPSTMP%"

It should read (changed version, compsize, exc_1_commands):

[DriverPack]
platform	= "wnt5_x86-32"
name		= "Graphics A"
; version 705
rootDir		= "D\G"
; OPTIONAL
classes		= "Display"
driverCount	= 4
decompSize	= 322
compSize	= 72.36


[A-1]
; REQUIRED
exc_count		= 2
; OPTIONAL
exc_1_tagFiles	= 2
exc_1_tagFile1	= "%SystemDrive%\ATICCC.ins"
exc_1_tagFile2	= "%DPSROOT%\D\G\A\1\ATICCC.exe"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
exc_1_-infFiles	= 0
exc_1_commands    = 3
exc_1_command1    = "%DPSROOT%\D\G\A\1\ATICCC.exe -y -o%DPSTMP%"
exc_1_command2    = "%DPSTMP%\setup.exe /s"
exc_1_command3    = "cmd.exe /c rd /s /q %DPSTMP%"
exc_2_tagFiles	= 2
exc_2_tagFile1	= "%SystemDrive%\ATICCP.ins"
exc_2_tagFile2	= "%DPSROOT%\D\G\A\1\ATICCP.exe"
exc_2_+hwids	= 0
exc_2_-hwids	= 0
exc_2_+infFiles	= 1
exc_2_+infFile1	= "%DPSROOT%\D\G\A\1\*.inf"
exc_2_-infFiles	= 0
exc_2_commands	= 3
exc_2_command1	= "%DPSROOT%\D\G\A\1\ATICCP.exe -y -o%DPSTMP%"
exc_2_command2	= "%DPSTMP%\Setup.exe /K"
exc_2_command3	= "cmd.exe /c rd /s /q %DPSTMP%"

The mobility.inf file still contains the errors I reported in this thread:
Invalid 'carriage returns' in any line that contains "ASUS Notebooks" (ati2mtag_M26 thru ati2mtag_RC410M)

;--- on ASUS notebooks (zorro1) ---
"ATI MOBILITY RADEON X700 (ASUS notebooks)" = ati2mtag_M26, PCI\VEN_1002&DEV_5653&SUBSYS_11B21043
"ATI MOBILITY RADEON X700  (ASUS notebooks)" = ati2mtag_M26, PCI\VEN_1002&DEV_5652&SUBSYS_19621043{1 funny characters are here}"ATI MOBILITY RADEON X700 (ASUS A6Rp)" = ati2mtag_M26, PCI\VEN_1002&DEV_5653&SUBSYS_11221043

"ATI MOBILITY RADEON X800" = ati2mtag_M28, PCI\VEN_1002&DEV_5D4A
"ATI MOBILITY RADEON X800 XT" = ati2mtag_M28, PCI\VEN_1002&DEV_5D48 {3 funny characters are here}"ATI RADEON XPRESS 200M Series" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62{1 funny characters are here}"ATI RADEON XPRESS 200M (ASUS A6Rp)" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62&SUBSYS_13921043{1 funny characters are here}

The odd characters don't show up in copy/paste into this post so I've substituted {funny character} entries instead.

From what I understand, if you remove the .CAT file, you also need to remove any references to that .CAT file from any .INF files.  All this breaks is "driver signing" (which is disabled by DP Base anyway).

If you don't modify any HWIDs in the INF files then the .CAT file can stay.  The .CAT file is the "driver signed" checksum for the package and will give errors if any of the included files don't match the checksum (INF, SYS, DLL).  The mobility.inf file doesn't have a .CAT file associated with it.

3,861

(8 replies, posted in Software)

This is why we need to put the english tutorial on the main page under "tutorials" hmm

Gantlett, you can find the english DP tutorial here
It should answer all your questions.

3,862

(76 replies, posted in 3rd Party DriverPacks)

Thanks Major!
Nice find.

Looks like Motorola split their drivers into x86 and amd64 subsets.  My Agere HWID is still listed though (VEN_ & DEV_) so I need to modify the INF in the Agere folder to match my HWID exactly in order to load first (VEN_ & DEV_ & SUBSYS_).
Any ideas on how to do that without breaking the CAT file?
*Edit
* Looks like the closest match to my HWID is in the directory D\3\M\A\2 ( D\3\M\A\3 looks to be an older exact duplicate of  D\3\M\A\2, it's even older than my gateway original drivers)
* The only differences I can see between the HWIDs in D\3\M\A\2, D\3\M\A\3, and my gateway INF is that the newer drivers (D\3\M\A\2) have a lot more HWIDs than the older one (D\3\M\A\3, duplicate HWIDs) but most have semi-colons to 'comment out' the lines.  What's the point in excluding all those HWIDs?  Can't we strip out the CAT file, add all the HWIDs into one INF and strip out the bloat?  Maybe it's time to start adding an INI exception to the pack?

Looks like we may see a modem DP v706 soon.  smile

*Edit #2
OK, I deleted the contents of D\3\M\A\3 and added my HWID to the INF of D\3\M\A\2 (also replaced all instances of "Toshiba" with "Agere" and deleted the CAT file).  Verified that this modified DP works fine on my Gateway notebook.  Sweet! smile

3,863

(16 replies, posted in DriverPack WLAN)

Arrrggghhh!
I feel like an idiot.
When I turn the wireless 'on' with the button on the notebook the HWID changes to:
PCI\VEN_1814&DEV_0201&SUBSYS_68331462&REV_01\3&267A616A&0&70: 802.11g MiniPCI Wireless Network Adapter

Notice the DEV_ change?

Sigh...
<mutters angrily> going off for more testing.  Remember to enable wireless before install!

Try replacing your GARTnt.INF file contents with this code and repack (added HWID and string):

;
; Copyright (c) 2000-2004 ATI Technologies Corporation
;
; GartNt.INF  -- This file contains descriptions of all the AGP Miniports
;             supported in Windows NT
;
; In order to install this driver, go to device manager, right-click on the PCI-PCI
; bridge which represents your AGP bridge and select "Properties". Then select the
; "Driver" page and push the "Update Driver" button. Go through the update driver
; wizard and on the "Locate Driver Files" page select "Specify a location" and then
; enter the location of your new INF and driver.
;

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGuid={4D36E97D-E325-11CE-BFC1-08002BE10318}
Provider=%ATI%
DriverVer=04/15/2005,5.0.2196.1015
CatalogFile = atisgkaf.cat

; =================== Common for all AGP devices =========================
[DestinationDirs]
DefaultDestDir = 12        ; DIRID_DRIVERS

[Manufacturer]
%ATI_MFG%=ATI_AGP

[SourceDisksNames.x86]
1 = %DiskId%,,,""

[SourceDisksFiles]
atisgkaf.SYS=1

[ControlFlags]
ExcludeFromSelect=*

[AGP_Filter_Reg]
HKR,,"UpperFilters", 0x00010000,"CABOAGP"
HKLM,"SYSTEM\CurrentControlSet\Services\caboagp","FW_SafeVideoCards",0x00030001,10,02

[pci_ServiceInstallSection]
DisplayName    = %pci_svcdesc%
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_BOOT_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
ServiceBinary  = %12%\pci.sys
LoadOrderGroup = "Boot Bus Extender"

; =================== ATI Chipset ========================
[ATI_AGP]
%PCI\VEN_1002&DEV_4371.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_4371
%PCI\VEN_1002&DEV_7010.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_7010
%PCI\VEN_1002&DEV_5838.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_5838
%PCI\VEN_1002&DEV_7838.DeviceDesc%=CABO_Install,PCI\VEN_1002&DEV_7838

[CABO_Install]
CopyFiles=@atisgkaf.SYS

[CABO_Install.HW]
AddReg = AGP_Filter_Reg

[CABO_Install.Services]
AddService = caboagp,0,caboagp_ServiceInstallSection
AddService = pci, %SPSVCINST_ASSOCSERVICE%, pci_ServiceInstallSection

[caboagp_ServiceInstallSection]
DisplayName    = %caboagp_svcdesc%
ServiceType    = %SERVICE_KERNEL_DRIVER%
StartType      = %SERVICE_DEMAND_START%
ErrorControl   = %SERVICE_ERROR_NORMAL%
ServiceBinary  = %12%\atisgkaf.sys
LoadOrderGroup = PnP Filter


; =================== STRINGS and CONSTANTS ========================

[Strings]
ATI_MFG = "ATI"
ATI = "ATI"
PCI\VEN_1002&DEV_4371.DeviceDesc = "ATI RADEON XPRESS 200M PCI to AGP Bridge"
PCI\VEN_1002&DEV_7010.DeviceDesc = "ATI RADEON IGP 340/340M/MOBILITY RADEON 7000 IGP AGP"
PCI\VEN_1002&DEV_5838.DeviceDesc = "ATI RADEON 9000/9100 IGP AGP"
PCI\VEN_1002&DEV_7838.DeviceDesc = "ATI RADEON 9000/9100 PRO IGP AGP"
DiskId       = "ATI Technologies Inc. Installation DISK (AGP)"

;service descriptions
caboagp_svcdesc = "ATI Cabo AGP Filter"
pci_svcdesc = "PCI Bus Driver"


;*******************************************
;Handy macro substitutions (non-localizable)
SPSVCINST_ASSOCSERVICE = 0x00000002
SERVICE_KERNEL_DRIVER  = 1
SERVICE_BOOT_START     = 0
SERVICE_DEMAND_START   = 3
SERVICE_ERROR_NORMAL   = 1

OK, here's what I found so far:
The ATI GART driver is in the Chipset DP D\C\AT\ and matches the official ATI driver exactly (your HWID are not listed)
From the GARTnt.INF:

In order to install this driver, go to device manager, right-click on the PCI-PCI
; bridge which represents your AGP bridge and select "Properties". Then select the
; "Driver" page and push the "Update Driver" button. Go through the update driver
; wizard and on the "Locate Driver Files" page select "Specify a location" and then
; enter the location of your new INF and driver.

So the ATI GART driver from the chipset DP should match your HWID here (but doesn't):
PCI\VEN_1002&DEV_5A3F&SUBSYS_00000000&REV_00\3&267A616A&0&08: Puente PCI estándar de PCI a PCI

There's also an error (possibly) in the latest nightly graphics_a DP that might be interfering with the install:
From the mobility.inf:

;--- on ASUS notebooks (zorro1) ---
"ATI MOBILITY RADEON X700 (ASUS notebooks)" = ati2mtag_M26, PCI\VEN_1002&DEV_5653&SUBSYS_11B21043
"ATI MOBILITY RADEON X700  (ASUS notebooks)" = ati2mtag_M26, PCI\VEN_1002&DEV_5652&SUBSYS_19621043{1 funny characters are here}"ATI MOBILITY RADEON X700 (ASUS A6Rp)" = ati2mtag_M26, PCI\VEN_1002&DEV_5653&SUBSYS_11221043

"ATI MOBILITY RADEON X800" = ati2mtag_M28, PCI\VEN_1002&DEV_5D4A
"ATI MOBILITY RADEON X800 XT" = ati2mtag_M28, PCI\VEN_1002&DEV_5D48 {3 funny characters are here}"ATI RADEON XPRESS 200M Series" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62{1 funny characters are here}"ATI RADEON XPRESS 200M (ASUS A6Rp)" = ati2mtag_RC410M, PCI\VEN_1002&DEV_5A62&SUBSYS_13921043{1 funny characters are here}

Basically, anywhere you find the keystring "ati2mtag_RC410M", somewhere in that line of code you'll find these odd/funny box characters (invalid CR?).

The mobility.inf is also missing some critical entries (taken from the ASUS drivers):

[ati2mtag_RC410M.Services]
AddService = ati2mtag, 0x00000002, ati2mtag_Service_Inst, ati2mtag_EventLog_Inst
AddService = Ati HotKey Poller,, Ati2evxx_Generic_Service_Inst, Ati2evxx_EventLog_Inst

[ati2mtag_RC410M.SoftwareSettings]
AddReg = ati2mtag_SoftwareDeviceSettings
AddReg = ati2mtag_RC410M_SoftwareDeviceSettings
AddReg = ati2mtag_Mobile_SoftwareDeviceSettings
AddReg = atioglxx_OpenGLSoftwareSettings
DelReg = ati2mtag_RemoveDeviceSettings
AddReg = ati2mtag_MobileLargeDesktopSettings

[ati2mtag_RC410M_SoftwareDeviceSettings]
HKR,, DALRULE_NOTVANDLCDONCRTC,             %REG_DWORD%,    1
HKR,, WmAgpMaxIdleClk,                      %REG_DWORD%,    0x20
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run",ATIModeChange,,"Ati2mdxx.exe"
HKR,, DALR6 CRT_MaxModeInfo,                  %REG_BINARY%,00,00,00,00,40,06,00,00,B0,04,00,00,00,00,00,00,3C,00,00,00 
HKR,, SMOOTHVISION_NAME, %REG_SZ%, "SMOOTHVISION 2.1"
HKR,, DisableQuickApply3D,                %REG_DWORD%,    1
HKR,, R6GxO_UseI2cLayer, %REG_DWORD%, 1
HKR,, GI_DEF, %REG_SZ%, 0
HKR,, ASTT_DEF, %REG_SZ%, 0
HKR,, ASD_DEF, %REG_SZ%, 0
HKR,, ASTT_NA, %REG_SZ%, 1
HKR,, 3to2Pulldown_NA, %REG_SZ%, 1
HKR,, Transcode_NA, %REG_SZ%, 1
HKR,, DALNonStandardModesBCD1, %REG_BINARY%,08,00,04,80,00,00,00,60,10,24,04,80,00,00,00,60,10,24,06,00,00,00,00,60,12,80,06,00,00,00,00,60,12,80,07,68,00,00,00,60,14,00,10,50,00,00,00,60
HKR,, ATIPOLLINTERVAL,             %REG_DWORD%,    2000
HKR,, ExtEvent_EnablePolling,      %REG_DWORD%,    1
HKR,, ExtEvent_BroadcastDispChange,      %REG_DWORD%,    0
HKR,, GCORULE_DisableHotKeyIfOverlayAllocated,          %REG_DWORD%,    1
HKR,, GCORULE_DisableHotKeyIfDDExclusiveMode,          %REG_DWORD%,    1
HKR,, ExtEvent_LCDSetMaxResOnDockChg,      %REG_DWORD%,    0
HKR,, GCORULE_DisableGPIOPowerSaveMode,   %REG_DWORD%,    1
HKR,, DALRULE_NOCRTANDDFPONSAMECONTROLLER,      %REG_DWORD%,    1
HKR,, GCORULE_IntTMDSReduceBlankTiming,      %REG_DWORD%,    0
HKR,, TVDisableModes,   %REG_DWORD%,    0
HKR,, GCORULE_ENABLERMXFILTER, %REG_DWORD%,   1
HKR,, DALRULE_RESTRICT2ACTIVEDISPLAYS,      %REG_DWORD%,    0
HKR,, DALRULE_POWERPLAYOPTIONCOLORDEPTHREDUCTION,      %REG_DWORD%,    0
HKR,, R6LCD_FOLLOWLIDSTATE,   %REG_DWORD%,    0
HKR,, DisableSWInterrupt,      		   %REG_DWORD%,    1
HKR,, ExtEvent_BIOSEventByInterrupt,      %REG_DWORD%,    0
HKR,, DisableD3DExclusiveModeChange,             %REG_DWORD%,    1
HKR,, DisableOpenGLExclusiveModeChange,             %REG_DWORD%,    1
HKR,, ExtEvent_EnableChgLCDResOnHotKey,                  %REG_DWORD%,    0
HKR,, DisableDalValidateChild,        %REG_DWORD%,    0
HKR,, DALRULE_ENABLESHOWACSLIDER,                  %REG_DWORD%,    1
HKR,, DALRULE_ENABLESHOWDCLOWSLIDER,                  %REG_DWORD%,    1
HKR,, R6LCD_RETURNALLBIOSMODES,              %REG_DWORD%,    1
HKR,, GCORULE_PPForceBlankDisplays,             %REG_DWORD%, 1
HKR,, ExtEvent_OverDriveSupport,      %REG_DWORD%,    1
HKR,, DisableAGPSizeOverride,      %REG_DWORD%,    1
HKR,, Main3D_DEF, %REG_SZ%, 3
HKR,, AntiAlias_DEF, %REG_SZ%, 1
HKR,, AntiAliasSamples_DEF, %REG_SZ%, 0
HKR,, AnisoType_DEF, %REG_SZ%, 0
HKR,, AnisoDegree_DEF, %REG_SZ%, 0
HKR,, TextureOpt_DEF, %REG_SZ%, 0
HKR,, TextureLod_DEF, %REG_SZ%, 0
HKR,, TruformMode_DEF, %REG_SZ%, 0
HKR,, VSyncControl_DEF, %REG_SZ%, 1
HKR,, SwapEffect_DEF, %REG_SZ%, 0
HKR,, TemporalAAMultiplier_DEF, %REG_SZ%, 0
HKR,, ExportCompressedTex_DEF, %REG_SZ%, 1
HKR,, PixelCenter_DEF, %REG_SZ%, 0
HKR,, ForceZBufferDepth_DEF, %REG_SZ%, 0
HKR,, EnableTripleBuffering_DEF, %REG_SZ%, 0
HKR,, ColourDesktopGamma_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, ColourDesktopBrightness_DEF, %REG_SZ%, "0 0 0"
HKR,, ColourDesktopContrast_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, ColourFullscreenGamma_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, ColourFullscreenBrightness_DEF, %REG_SZ%, "0 0 0"
HKR,, ColourFullscreenContrast_DEF, %REG_SZ%, "1.0 1.0 1.0"
HKR,, 3D_Refresh_Rate_Override_DEF, %REG_DWORD%, 0
HKR,, Display_Detection_DEF, %REG_DWORD%, 0
HKR,, Panning_Mode_DEF, %REG_DWORD%, 0
HKR,, Mouse_Track_Orientation_DEF, %REG_DWORD%, 1
HKR,, Force_TV_Detection_DEF, %REG_DWORD%, 0
HKR,, CatalystAI_DEF, %REG_SZ%, 1

[ati2mtag_RC410M.GeneralConfigData]
MaximumDeviceMemoryConfiguration=256

I'll report back if I find anything else.  So far you have two problems:
1) Chipset DP missing your HWID (GARTnt.INF).
2) Badly formated mobility.inf in Graphics_A DP

I'm checking the MassStorage DP now for the IDE controllers.
*Edit
MassStorage DP is good.  Your HWID is listed.

I am going to try to tackle this over the weekend. 
Just because the driver has the same filename doesn't make it the same driver (found out the hard way).

I'll try to repackage the integrated chipset catalyst suite as a test.
Maybe the main team can add an exception to the ini file as a test too.

3,867

(76 replies, posted in 3rd Party DriverPacks)

I will look into this again.  I can test the Agere hardware that's in my notebook. 
There must be an easier way to scan for conflicting HWID in the INF files in the DriverPacks...isn't there? hmm

That's a good question!
I'll take a look when I get home from work.  I know that the xpress 200m chipset is not supported by the 'official' ATI catalyst suite, it's supported by separate dl because of the integrated chipset drivers.  It's possible that the graphics-half & chipset-half are included in the graphics_a/chipset DriverPacks respectively in which case all you'd need to do is verify driver locations and edit the inf's accordingly.
That could be answered by someone from the main team or someone intimately aware of the DP's composition.

Major wrote:

Chipset: ATI Radeon Xpress 200M
Graphic Card: ATI Radeon Xpress 200M series

The ATI Radeon Xpress 200M is not supported by the Catalyst drivers in the Graphics_A pack.  This was discussed in this thread:
http://forum.driverpacks.net/viewtopic.php?id=1504

The 200M series is supported by a separate download. Here: http://ati.amd.com/support/drivers/xp/i … ed-xp.html
I suppose you could make that into a 3rd party driverpack.

And why are you using DPBase 7.04 with 7.05 nightlys?
Kind of a mismatch don't you think?

Intel just released v8.2.0.1014 on 7 May 2007 here:
http://downloadcenter.intel.com/detail_ … p;lang=eng
It is the same drivers (but newer) we use in the chipset pack D\C\I\xp\ directory.
Can we get a 7.05.2 release?  smile

3,872

(12 replies, posted in DriverPack Chipset)

Intel just released v8.2.0.1014 on 7 May 2007 here:
http://downloadcenter.intel.com/detail_ … p;lang=eng
It is the same drivers (but newer) we use in the chipset pack D\C\I\xp\ directory.
Can we get a 7.05.2 release?  smile

I'm not sure what those other drivers are for that Fragbert posted.  Looks like they only support Intels own motherboards.

There is currently a debate going on in another RVM forum thread regarding addon pack version/revision numbering.
http://www.ryanvm.net/forum/viewtopic.php?t=4694

Not everyone can agree. smile

3,874

(88 replies, posted in Feature Requests)

jtdoom wrote:

they do not suffer a dime.

Maybe not, but M$ still hates the fact that Vista is not making the impact in the marketplace that they were anticipating.  The 'acceptance' numbers we're seeing in the media are combined retail/OEM/upgrade/express-upgrade numbers (OEM can be discounted based on the numbers of users reverting back to XP) and I can almost guarantee that those numbers are inflated or rounded off to the nearest million.
big_smile

On licensing: I found this VERY interesting reading.
From M$ own download page (word doc):
http://download.microsoft.com/download/ … _chart.doc

Can I downgrade my OEM version of Windows Vista Business to Windows XP Professional?

Yes. OEM downgrade rights for desktop PC operating systems apply to Windows Vista Business and Windows Vista Ultimate as stated in the License Terms. Please note, OEM downgrade versions of Windows Vista Business and Windows Vista Ultimate are limited to Windows XP Professional (including Windows XP Tablet PC Edition and Windows XP x64 Edition). End users can use the following media for their downgrade: Volume Licensing media (provided the end user has a Volume Licensing agreement), retail (FPP), or system builder hologram CD (provided the software is acquired in accordance with the Microsoft OEM System Builder License). Use of the downgraded operating system is governed by the Windows Vista Business License Terms, and the end user cannot use both the downgrade operating system and Windows Vista Business. There are no downgrade rights granted for Windows Vista Home Basic or Windows Vista Home Premium.

So basically, if you get Vista Business/Ultimate, your vista license INCLUDES a license to revert to XP, but the user would be responsible for providing their own XP install media (VLK, retail, OEM).

3,875

(88 replies, posted in Feature Requests)

OverFlow wrote:

I'm reverting yet another laptop loaded with Vista to XP for a customer that just hates Vista.

Get used to it...I've reverted two laptops this week.  smile
It's a trend...one that M$ won't like.