1

(30 replies, posted in Windows 7 Discussion)

Duly noted. Daddy needs a new pair of shoes!

Great pics Samlab!

2

(30 replies, posted in Windows 7 Discussion)

Yikes!
I take it that he was not the repairman? smile

3

(18 replies, posted in Windows 7 Discussion)

Good to hear. Let me know if you think of anything else.

As a side note, nothing was as frustrating as trying to figure out why DISM kept failing. I have my xbox360 controller drivers, an infrared remote receiver device (non-MS) and soundmax hd audio which all integrated without incident using DISM. It just so happens that what these three had in common were no files ending in underscore (compressed). Even after decompression it was a no go to which later on I found that the uncompressed file had to retain the underscore.

I'll be more than happy to help with driverpacks if I find the time. Please let me know.

4

(18 replies, posted in Windows 7 Discussion)

This is done. Use link above and let me know if works out.

NOTE: You must enclose directory in commandline in double quotes. "C:\MY DRIVERS" Trailing backslash optional.

5

(18 replies, posted in Windows 7 Discussion)

I'll keep it the way it is for non-command line. As long as you feed it a path, I don't see why it shouldn't work this way. I will work on it today. It is very easy to do. Will let you know.

6

(18 replies, posted in Windows 7 Discussion)

Not too off topic, but when a batch starts hitting a brick wall I usually run to vba or autoit since it's simple file manipulation. For more severe projects I'll to delphi. If you need help with those batches let me know.

7

(18 replies, posted in Windows 7 Discussion)

This is a compiled autoit (non macro). I didn't think it warranted pascal - which is the only language I code in. However, if you find it would be useful in delphi, I'll see if I have some time to port over. If it's even worth it...?

I can probably open it up to accept command lines and you can just include it in whatever you're working on. Either way pants.

Let me know.

smile

8

(18 replies, posted in Windows 7 Discussion)

No sweat. It works great with already expanded files.

9

(18 replies, posted in Windows 7 Discussion)

I have coded a new decompressor...hopefully this will get rid of nasties the likes of which midi found.
All I need to know now is how to u/l! smile





EDIT: Try this link: http://cid-8977a3dbe8c60076.skydrive.li … RVPREP.exe

10

(18 replies, posted in Windows 7 Discussion)

Yes, the delims is putting a wrench in the batch. Fantastic stuff Alex, I'll probably leave the batch and put something together in code.


EDIT: Thinking of making this super silent and maybe you can integrate it into a script. I'll use an ini for directory pointer. Yes?

11

(30 replies, posted in Windows 7 Discussion)

midiboy,

I posted a batch for this issue on a different topic, if you're interested.

I would appreciate anyone belonging to driverpacks development to maybe investigate why such a fine project is not working for everyone on W7. Don't get me wrong, if dism integration is working for you then I am happy. Good deal. Otherwise, you're not being much help.

For those who have been having trouble with driver injection, it is a known issue that has been widely discussed at TechNet. Although "issue" may be a misnomer, more like a change in fuctionality...as much as it sucks.

See here for an excellent example as referred to by MS Connect:
http://social.technet.microsoft.com/For … 35de8fe6b5

12

(18 replies, posted in Windows 7 Discussion)

Thanks for the tags pants smile

In any case, this is a known issue as reported on TechNet. I have been trying the expand thing with no luck until a user there suggested expanding and leaving the underscore. Genius! Hopes this helps those that come across this issue.

13

(30 replies, posted in Windows 7 Discussion)

Really? Must be new with RTM...will try it out.

Thanks muiz


EDIT: Still needs expanding. Still reports "The driver package could not be installed" message.

14

(18 replies, posted in Windows 7 Discussion)

I have been working on this for my own personal DVD for quite some time. Downloading the drivers (using video as an example) and simply uncompressing to a folder will not work if you are planning on injecting them into your W7 image. DISM will fail on /add-driver.
In any case, you must use EXPAND all files ending with an underscore character ( _ ) while leaving the underscore intact.
In my case, I'm downloading a new nVidia package every few months (amongst others) and so I am constantly having to expand these. I've created a batch that makes this effortless so feel free to use. Remember to expand your install.exe into a folder and run the batch against it (changing the directory names to reflect yours). Copy and paste to notepad and save as filename.bat. You may then properly run DISM on the drivers.

This has been tested on nVidia and ATI...working.

REM @echo off
REM Batch file for conversion/expansion of any driver files that do not cooperate with Windows 7 DISM ADD-DRIVER due to compression.
REM This will also parse subdirectories and expand those files as well.
REM For visual confirmation, be sure to refresh your directory to view correct file sizes.

REM Location of original driver directory	                                (user defined, don't forget trailing backslash)
SET DRVDIR=E:\VISTA\DRIVERS\nvidia

REM Wildcard pattern to search for compressed files		(this example for nvidia, NVAPI.DL_)
SET WILDCARD=*.??_

REM Holds directory\filename of original compressed files 	(user defined, may be left unchanged)
SET DRIVERS=C:\DRVORG.TXT

REM Holds directory\filename of expanded files		(user defined, may be left unchanged)
SET EXPANDED=C:\DRVEXP.TXT

REM Creates log of commands
SET LOG=C:\COOLLOG.TXT

REM Pre-Cleanup
DEL %EXPANDED% /q
DEL %DRIVERS% /q
DEL %LOG% /q

REM  Creates standard text file with directory\filename of compressed files
for /f "tokens=1,2,3,4,5 delims= " %%A in ('dir /b /s %DRVDIR%%WILDCARD%') do echo %%A >> %DRIVERS%

REM  Creates second standard text file with directory\filename of expanded files (minus the third ext character (underscore))
for /f "tokens=1,2,3,4,5 delims=_" %%A in ('dir /b /s %DRVDIR%%WILDCARD%') do echo %%A >> %EXPANDED%

REM Expands files to same directory (expanded files now have only two character extension)
for /f "tokens=1,2,3,4,5 delims= " %%A in ('type %DRIVERS%') do EXPAND.EXE -R %%A >> %LOG%

REM Overwrites original files
for /f "tokens=1,2,3,4,5 delims= " %%A in ('type %EXPANDED%') do MOVE /Y %%A %%A_ >> %LOG%

REM Cleanup
DEL %EXPANDED% /q
DEL %DRIVERS% /q

REM Present log file
CALL NOTEPAD.EXE %LOG%

EXIT

15

(30 replies, posted in Windows 7 Discussion)

As I don't know the particulars of ATI drivers, I can tell you now that integration will fail on the nVidia side. You must expand the files while retaining the underscore character for slipstreaming to work in W7.

16

(9 replies, posted in Windows 7 Discussion)

I see. You can also go this route...

WIN+R > CONTROL USERPASSWORDS2 > ADVANCED TAB > ADVANCED

17

(9 replies, posted in Windows 7 Discussion)

Very intriguing...hmm.

CONTROL PANEL >> SYSTEM AND SECURITY >> ADMINISTRATIVE TOOLS >> COMPUTER MANAGEMENT?

In Computer Management (Local) > System Tools > Local Users and Groups > Users - you may have that exact ability. I never tried to learn more about it as far as command line options and such, but Holy Cow if you can research this that'll be something, eh?

I must admit...why this option? (Disabling...Lockout I can barely understand) I've used it to piss my mother-in-law off in the past.

18

(10 replies, posted in Windows 7 Discussion)

Alright, I see what's happening within the Graphics A.
These seem to be OOB drivers of sorts with no control panel or physX capabities whatsoever (at least on the NVIDIA side). What you must do, muiz is to get all the latest drivers and expand all *.??_ files without renaming them (keeping the last _ intact). Dism has a heartattack when these are not expanded on any recent driver files. This also holds true for ATI drivers and has been verified to work. I have done my own tests and can confirm that nvidia control panel does appear as well as physX properties within the control panel (process offload). As for AGEIA Technologies (physX) folders appearing in Program Files, it does not. I suppose that can be installed seperately (and silently?).

181.71 does not support offloading to mix gpus, which is a must for me. smile This can only be accomplished through the CPL. I believe mixed gpu support arrived in 185.81 (official for W7x32, at least). Please let me know what your thoughts are...

19

(10 replies, posted in Windows 7 Discussion)

Right on Muiz. Reason I asked was because of the headaches that dism has been causing me with regard to nvidia /add-driver. I've since figured it out. Looking forward to your W7 contributions!

20

(10 replies, posted in Windows 7 Discussion)

It's been quite a while since my last post (a year or two?).
Have we verified that in fact nvidia drivers are correctly streamed into W7 image?

@muiz... mce = xp pro not necessarily true. Try installing latest xp nvidia drivers on an mce machine...! smile

Did you compare working unattend cd and bad unattend's WINNT.SIF? You may want to post both of those versions.

Huh... Anyone know if spaces before and after '=' make a difference if WINNT.SIF?

It's most likely massstorage. Play around with that for awhile. I've used driver packs exclusively with MCE (never a problem with the nvidia drivers even! Always installed correct drivers)...only problems I've ever encountered (regarding bsod) was mass storage.

Wow...it's ultimate Geek Porn!

The driver packs will have no bearing on MCE functionality. I have been using drivers packs solely on media center with fantastic results.