1 Reply by thatwill

(524 replies, posted in Windows 7 tools)

Should be quite simple to fix the cleaning phase (at least in non-silent mode - it should still go through as normal in silent mode..)
On version v13.04.28, replace line 310:

IF /I "%option%"=="Y" SET "CLEAN=Y"

with:

IF /I "%option%"=="Y" (SET "CLEAN=Y") ELSE (SET "CLEAN=N")

haven't tested yet but no reason why it shouldnt work.

Edit: Just noticed that it was meant to be fixed in 13.04.26 - I couldn't see a fix in .28, but ignore if it's already working!

Go to forum: Windows 7 tools

2 Reply by thatwill

(524 replies, posted in Windows 7 tools)

Hi guys, found a little bug in SAD3-130423.

If running with no parameters, the variable %CLEAN% is never set to N, so the clean always happens regardless of what the user chooses.

Go to forum: Windows 7 tools

3 Reply by thatwill

(18 replies, posted in Vista / 7 DriverPack WLAN)

TechDud wrote:

Some connection issues with specifically BCM4313 are resolved, if you can get your hands on a generic v5.100.82.143 (or later if applicable) for Vista-7 (IIRC).

The BCM430N v5.100.82.135 driver included in the driverpack works fine with my device, but only if I edit the inf file. Does this break driver signing and therefore break the driver installation?
I can't seem to find a generic driver which includes this device.

Go to forum: Vista / 7 DriverPack WLAN

4 Reply by thatwill

(18 replies, posted in Vista / 7 DriverPack WLAN)

Not sure if this is the right place to report... I've noticed that the latest beta pack is missing a broadcom wifi driver -
VEN_14E4&DEV_4727&SUBSYS_7179144F&REV_01
This is present in a Samsung RV511 laptop.

The driver from the Samsung site is here. This is a BCM43XX driver, a newer version of which appears to be already present in the driver pack. However the newer version doesn't have this subsys in the INF file.

Not sure if merging the INF files is enough, but it appears to install and connect to an access point fine if I add the missing SUBSYS line. If it's easier, the inf file is here

Go to forum: Vista / 7 DriverPack WLAN

5 Reply by thatwill

(524 replies, posted in Windows 7 tools)

Hey Steve, sorry I missed the 2.7; just checked back at the forum now. I'll test the 3.0 out as soon as I can.

Question in the meantime, which i'd been wondering for a while.. in the ":Continue" section of the script, it echoes "Verifying..." but then just makes the system wait for 60 seconds. Is there a reason this delay is needed, whilst there is seemingly no other process going on?

Anyway, many thanks for the effort here; i'll let you know once I've been able to give it a good test.

Go to forum: Windows 7 tools

6 Reply by thatwill

(524 replies, posted in Windows 7 tools)

Hey,

Firstly, thanks for the SAD guys, it's fantastic.

I'm currently using SteveDun's 2.5 modded version, but i'm still getting several different touchpad driver applications installed on the system. Cypress, ELAN, Synaptics and Alps are all getting installed. I've tested this a few times and sometimes it can result in the touchpad not working until I uninstall the software again.

So in the changelog for 2.5, it's mentioned that the touchpad issue should be fixed. I can't see what's been changed in the code to fix this however. What should have fixed the issue - is it just the newer version of DPInst?

I'm testing on a Tosh laptop with Win7 64-bit, with the options set up at the start of the script:

SET "SILENT=Y"
SET "CLEAN=N"
SET "REBOOT=R"
SET "KTD=N"

I'm using "DP_Touchpad_Mouse_wnt6-x64_1203", and i've also tried some newer packs from the forums, with the same sort of results.

The hardware ID for the touchpad on this system is ACPI\TOS0300, and the drivers from the Toshiba site for this laptop are Synaptics.

Don't know if this is an issue with SAD or the driverpacks/dpinst. If anyone wants to take a look, here's the dpinst.log file. I'm not exactly sure what i'm looking for in this log, but there's a few instances of touchpad drivers being installed then rolled back by dpinst - i guess it's possible that the driver software wasn't rolled back at the same time as the driver.

Thanks!

Go to forum: Windows 7 tools