Bâshrat the Sneaky

BTS DriverPacks BASE V5.07.2 Changelog: V5.07.2 (05 Jul 05) -Fixed: [DPM] slipstream_DPM.cmd, winnt.exe/winnt32.exe: hptmv6.sys was missing in dosnet.inf. -Fixed: [DPM] copy_sys_files_to_temp.cmd, multiboot: hptmv6.sy_ was missing: it would not get copied. Download Known issues -Bug|non-critical: [DPB] all methods: in winnt.sif: if a section is being updated with new and/or updated entries, it will add a new section if the cases of the sectionname aren't identical. -To-do [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it. @Siginet: your second post to 'clarify things' was quite... superfluous. No offense, heh!

DriverPack Chipset V5.07 Supported devices. Changelog: V5.07 (05 Jul 05) -New: support for ATK0110 ACPI utility (found on many ASUS motherboards: ACPI controller). -New: support for ITE CIR (Consumer InfraRed remote control). -New: support for VIA IR (InfraRed). -Updated: VIA Hyperion 'mach' driver from 10/02/2002,5.1.00.0230 to 10/02/2002,5.1.00.0240. Download

Which 'Aureon' control panel? The 'Sky-Space-Universe' one? Or the 'Fun' one? I've searched with google and came up with this topic on some forum. So what did I do? I just downloaded the AIBooster program and found the drivers in there. I'll update DriverPack Chipset It might be better if you'd start such a topic yourself: that gives you the chance to explain everything in detail in the first post.

I've just bought myself new hosting, and the 3 DriverPacks that are still online (except for the DriverPacks BASE of course) are already moved to that server. Now I'm moving the others there as well. Though I didn't expect this server to go offline, I wasn't notified, nor aware this would happen... Now I'm moving the files faster than I would if this server didn't go offline... @mjc: check your PM's EDIT: Graphics A is also available again. Uploading the last three (about 100 megs, will take some time...)

DriverPacks Chipset & CPU are moved to an alternative server. Uploading also DriverPack Graphics A to an alternative server.

WTF.... there's no renaming ANYWHERE and the file Methods_V507.7z does NOT EXIST in the DriverPacks BASe V5.07.1, so I'm wandering what could be causing this???

Thanks, didn't know this host was offline. Note that BASE, Graphics A, LAN and MassStorage are not affected by this failure. I've contacted the responsible right away, I'll keep you updated. This is not a problem related to bandwidth: the host is not reachable (nor through ping, nor through SCP). Topic moved to DriverPacks General Discussion.

I have Methods_5071.7z in my files folder but in my UWXPCD_Root\M2 folder it's called Methods_507.7z and of course it gets left in the root on my XPCD folder when i slipstream it...??? is the Methods file not required at all anymore, whatever Version it is..? ← Eh... maybe that file is still there because you completed step 1 with the 5.07 version? Then it's possible... You should then redo step 1 (and 2 & 3 of course, using DPs BASE V5.07.1. Other than that... I would not know what's happening...

Should I laugh or should I cry? At least ONE vendor that updates its drivers frequently => laugh ... too frequently? => cry

Checked.

@muiz & Siginet: there shouldn't be a Methods_V507.7z in the DriverPacks BASE V5.07.1... Did you update manually, muiz? Maybe you forgot to delete the file? @Siginet & cybpsych: did you also have this problem with the previous version (V5.06)? @cybpsych: I just tested and it DOES copy all DriverPacks :s How could it not? Just check the code: SET D=DriverPack SET FOLDER=UWXPCD_ROOT SET RS=%ROBOCOPY_SWITCHES% ... ROBOCOPY %D%s %FOLDER%\DPfiles %D%_*.7z %RS% > NUL @muiz: I checked, the driver used is still the si3112r driver... didn't change anything, as I already thought. The only thing that has changed, is that I'm using a newer version of the si3112r driver... and that I added a si3112 driver that's required for some SiI 3112 SATALink controllers on some ATI chipset motherboards. In theory it should still be working fine, but in reality, as you can see... Could you please re-check your HWID, and post the complete HWID? (The one with "&REV_????".) P.S.: according to the driver's .inf file, your controller is NOT a 3512, but a 3112!

Eh... many have a working disc here... Are you sure you aren't doing anything wrong??? I'm also quite sure I've seen this motherboard's nvraid reported working before. Please attach your winnt.sif.

THROW AWAY those 2 19" LCD's. They've got huge, ougly pixels! Instead, go get yourself 2 Dell 2005FPW's: superfast (16 ms) widescreen monsters, fantastic for graphics & design!

My DriverPacks are meant for unattended Windows installations, at least in the form I'm offering you them as downloads. If you simply want to use them from Windows, you should extract them with 7-zip/WinRAR/PowerArchiver/... (7-zip is free) and then let Windows search in the extracted folders for the appropriate driver. Hopefully (and very probably), it'll install your driver.

It should be working like it is... Though it would help if you'd tell me which version DOES work for you!

BTS DriverPacks BASE V5.07.1 Changelog: V5.07.1 (03 Jul 05) -Fixed: [DPB] RUN_ME.cmd, ROE: cmdlines_fix.exe didn't get executed, nor was it deleted. (bug introduced in V5.07) Download Known issues -Bug|non-critical: [DPB] all methods: in winnt.sif: if a section is being updated with new and/or updated entries, it will add a new section if the cases of the sectionname aren't identical. -To-do [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it.

@midiboy & Siginet: I'm determined to change to my old habit again - I've always been but finally I have the time again: update as soon as a bug has been found. That's why you can expect a fixed version in a few minutes.

BTS DriverPack MassStorage V5.07 Supported devices. Changelog: V5.07(03 Jul 05) -New: support for nVidia nForce 4 Intel Edition mass storage controllers. -Updated: Intel SATA RAID drivers from 12/17/2004,4.7.0.6815 to 03/09/2005,5.0.0.1032. -Updated: nVidia nForce mass storage controllers drivers from 02/11/2005,5.10.2600.0518 [5.18] to 05/26/2005,5.10.2600.0535 [5.35]. Download

DriverPack LAN V5.07 Supported devices. Changelog: V5.07 (03 Jul 05) -New: added support for nVidia nForce ethernet (Intel). -Updated: Marvell Yukon LAN controller driver from 04/28/2005, 8.27.3.3 to 05/06/2005, 8.27.4.3. -Updated: SiS 190 & SiS 191 LAN controllers driver from 02/18/2005,2.0.1039.1030 [1.03b] to 05/24/2005,2.0.1039.1040 [1.04]. Download

BTS DriverPacks BASE V5.07.7 Changelog: V5.07.7 (31 Jul 05) -Updated: [DPSA]: BTS_DPs_finish.cmd: VIA Vinyl driver control panel installation updated. V5.07.6 (29 Jul 05) -Fixed: [DPM]: copy_sys_files_to_temp.cmd: obsolete nvcchflt.sys entry were still added. -Fixed: [DPM]: slipstream_DPM.cmd: obsolete nVidia nForce entries were still added. -Fixed: [DPM]: slipstream_DPM.cmd: Silicon Image SiI 3512 SATALink controller may be working again now (work-around attempt). V5.07.5 (28 Jul 05) -Fixed: [DPB]: KtD, M2: fixed the annoying Driver Signign Policy popups. -Fixed: [DPM]: slipstream_DPM.cmd: nvcchflt.sys entries for dosnet.inf were still added. -Fixed: [DPM]: slipstream_DPM.cmd: nVidia nForce drivers failed to install during textmode setup. V5.07.4 (25 Jul 05) -Removed: [DPB]: the 'experimental' tags for the Keep the Drivers (KtD) & RunOnceEx options. -Fixed: [DPM] slipstream_DPM.cmd: added a new HWID for the hpt3xx driver. -Improved: [DPM] slipstream_DPM.cmd: the nVidia nForce 1/2/3/4 drivers have been split up into 5 groups of drivers. This was possible thanks to the updated drivers. This should (let's all hope so) fix all the problems with these chips. V5.07.3 (06 Jul 05) -Updated: [DPB] 7za.exe from 4.23 to 4.24b. -Fixed: [DPM] slipstream_DPM.cmd: fixed the problem with one (probably multiple) Silicon Image 3512 SATALink controller, by adding support for the updated driver in the updated DriverPack MassStorage (DP MassStorage V5.07.1). -Fixed: [DPM] slipstream_DPM.cmd: added a specific HWID for ABIT KV-80's VIA VT8237 controller, that uses the viamraid driver. V5.07.2 (05 Jul 05) -Fixed: [DPM] slipstream_DPM.cmd, winnt.exe/winnt32.exe: hptmv6.sys was missing in dosnet.inf. -Fixed: [DPM] copy_sys_files_to_temp.cmd, multiboot: hptmv6.sy_ was missing: it would not get copied. V5.07.1 (03 Jul 05) -Fixed: [DPB] RUN_ME.cmd, ROE: cmdlines_fix.exe didn't get executed, nor was it deleted. (bug introduced in V5.07) V5.07 (03 Jul 05) -Updated [DPB] 7za.exe: from 4.20 to 4.23. -Fixed: [DPB] RUN_ME.cmd, ROE: cmdlines_fix.exe didn't get deleted. -Fixed: [DPM] slipstream_DPM.cmd: 'rhpt3xx.sys' entry was missing in dosnet.inf. -Fixed: [DPM] slipstream_DPM.cmd: a lost 'hptmv6' entry was wandering around in txtsetup.sif. -Fixed: [DPM] slipstream_DPM.cmd: added a specific HWID for MSI K8T Neo's VIA VT8237 controller, that uses the viasraid driver.. Download Known issues -Bug|non-critical: [DPB] all methods: in winnt.sif: if a section is being updated with new and/or updated entries, it will add a new section if the cases of the sectionname aren't identical. -To-do [DPM]: the Promise misery... making a driver of myself would be the only 'easy' and 'painless' way to solve it.

It *could* be installed, but my DriverPacks are meant as an addition, to complete Windows XP's drivers range. Moved to DriverPacks General Discussion.

As I said earlier, I will combine all messy Promise drivers into one clean driver. Though this might take some time, then all our problems will be solved!

@borgie: could you also post the HWID of that other board that you were having problems with? Thanks. Your problem should be solved in DriverPacks BASE V5.07/DriverPack MassStorage V5.07 by the way. @d3tr0it: as you know, that is no real solution. So if you could please post your HWID, I could add it to make a 'real' solution

That option is already there... check method 1 And by the way, you could create many 'new' hybrid methods. That's indeed planned for the next releases, as well as many more improvements. Also this is on the future features list. And I can tell you that there are not many RIS users. Only 10-30.

no up-time/speed problems at all?