Implemented in \TP for DriverPack WLAN 12.02 (in testing)

602

(20 replies, posted in DriverPack WLAN)

Implemented in \R & \R6 for DriverPack WLAN 12.02 (in testing)

603

(19 replies, posted in DriverPack WLAN)

Implemented in \Br0 for DriverPack WLAN 12.02 (in testing)

LOL, discussing licensing is like opening a can of worms.  I am not a lawyer, nor do I represent myself as such.
To be clear, the "component utilities" of the SAD2 "package" are distributed under their respective licenses.  The SAD2 "source code" I am distributing under the CC (BY-SA) 3.0. license.
So the entire "package" is distributed under a variety of licenses and is not bound by a single license.

The direction these recent posts are heading is detracting from the original post.
To answer the question: Yes, I can rip the guts out of the script to enforce x64 installation, but I won't.  It does everything I need it to do and does it safely.
Please create a new thread to discuss the relative merits of the FOG utility.

I'll most likely break the signing to remove that line.  But I haven't yet had time to do anything with it.
I've made this a priority since it's a pretty bad bug.  I just don't have a lot of time lately with "real life" getting in the way.

@andyroo54, well if that's the case than whatever you did to build the sfx is broken.  Don't use it.  I'm still baffled as to why you'd want to convert it to sfx in the first place when you've said it works fine as-is.  CMD-2-EXE utilities often translate the code badly and usually force the code to run in a 32-bit space which may confuse the 64-bit checks.

Updated first post to new v120203.  Now packed as a 7-zip self-extracting archive for those without native 7-zip.
To-do: Update code to take advantage of native WinRAR if installed

As an example, on my Intel Q6600 CPU I get the following:
c:\>echo %PROCESSOR_ARCHITECTURE%
AMD64

c:\>echo %PROCESSOR_IDENTIFIER%
Intel64 Family 6 Model 15 Stepping 11, GenuineIntel

Are you sure you're on x64-bit hardware?
Please open a command-window prompt on the target machine and type the following:
echo %PROCESSOR_ARCHITECTURE%
echo %PROCESSOR_IDENTIFIER%

Then post back here with the responses to each command.  It would be interesting to see what your CPU is reporting.  I may have to alter the code to cope with alternative CPU reporting.
You can over-ride the batch file, but there shouldn't be a reason to.  I wrote those safeguards to ensure the correct packs were installed.

To make the script fully automated, just remove the "set option" line 165:
:KTD-option
set /p option=[Y,N]?

That's a great find!
We refer to that type of HWID a "super-generic". 
I'll need to fix that!  Thanks! big_smile

Thanks, I'm sure that will be fine.

OK, the XP drivers are older than the generic Intel ones, but the Win7 drivers are newer.
But, although newer, they're still not a direct replacement for the generic Intel ones because not all HWIDs are represented.
I'll move this to the Win7 area and I'll try and update the packs with both updates.
...moving to Win7 section...

I'll take a look.  I've got the generic Intel wifi package (10/27/2011,14.3.0.6) in a test build.
Looks like the v15.0.* builds are for Win7, not XP.

Well why did you post in the NT5 area then? hmm
jmide.inf is from 2006.  I don't think it's needed for Win7.
...moving thread to Win7 area...

616

(1 replies, posted in DriverPack Sound)

Can you post your HWID list and provide a link to drivers that are known to work?

OK, I streamlined the code a bit and implemented the native 7-zip extraction.
The command line version of 7-zip doesn't have a pretty progress bar, but it has speed! big_smile
Just doing a test extraction between the old un7zip and the native 64-bit 7z.exe shaved 10 seconds off the extraction of the 64-bit audio dp.

I still have not tested LZMA2-compressed DriverPacks yet but we still need to maintain backwards compatibility with older versions of SAD2.

All very good ideas.  I'll see about implementing them.  I need to check to see if the installed versions of 7zip allow for scripted actions.

Nice to see you finally made it over here bphlpt! big_smile  Welcome to DriverPacks.
The un7zip.exe utility we use was created back in 2010 and doesn't support LZMA2 compression.  It's possible that it may be updated but that is beyond my capability and I don't have the source code.
I suppose I could alter the script code to peek at the host system for 7zip install and if it exists, use the built-in app instead of our older utility.
hmmmm.

620

(4 replies, posted in Software)

My 9yr-old daughter learned how to use it without any external instruction.
Google is your friend.
This is a DriverPacks support forum!

http://dpsdl.drupalcdn.netdna-cdn.com/other/icon_lock.gif

Glad to be of service.

622

(10 replies, posted in DriverPack LAN)

I'll take a look.  It's possible we can use this elsewhere.

623

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

On behalf of the entire DriverPacks team, Thank you...and You're welcome!
smile
Welcome to DriverPacks.  It's not often someone pops in to say thanks.
Donations are a rare occurrence.
Once Wim confirms the donation, He'll change your status to "donor".  You'll notice that as a "donor", you will have several new areas of the forums unlocked to you for exploration.

624

(3 replies, posted in Software)

One of our goals is to have a tool that does exactly what you describe.
Scan the target system for HWIDs, compile a list of drivers needed from our database, extract the drivers required for the target system, inject the drivers.
Unfortunately we're not there yet.
There are several 3rd party tools in these forums you're welcome to try, but they are not supported by us.
The only one that we support that comes close to your requirements is SAD2.  But it does not support downloading DriverPacks (they must be present in the provided folders prior to execution).
http://forum.driverpacks.net/viewtopic.php?id=5336

625

(5 replies, posted in DriverPack LAN)

I got your  F^<#ing drivers right here! wink

v12.01
Updated
- I\ Intel from 16.8.1 CD (1/20/2012)
- J\ JMicron JMC25x/JMC26x NDIS 5.x MINIPORT DriverVer = 11/17/2011, 5.0.33.3
- M\ Marvell Yukon Ethernet Controller to 01/20/2012, 11.45.3.3
- R4\ Realtek 10/100/1000 PCI-E NIC Family NDIS XP DriverVer = 12/08/2011,5.792.1208.2011