it does but when you go to windows updates it reports that there is a newer driver.
and the driver that is included with windows works but the one that gets used from the packs does not.
i have been able to avoid issues by installing vmware tools @ t-13 or so (cmdlines.txt / runonce.cmd file)

4,552

(42 replies, posted in Other)

or he could use the button marked "pause" on the keyboard and not mess with the bios???

but then he wouldn't be haveing any fun rubbing it in would he wink

4,553

(74 replies, posted in Vista-Tool)

its time, I said SP1. smile rats... wink

Welcome to DriverPacks dado023,

No need to aplologize. Many people here do not speak english as thier primary language, Bâshrat the Sneaky included.

If you have found your way here by the route you described it is likely you will become a regular - sorry... wink

It works because it is a feature that is, and has been, built into windows.
if microsoft did not offer an avenue for OEM's to add the required drivers to windows setup
then it would be very costly to mass produce machines.

there is probably a reference driver for your 1100 in the packs but since laptops are so picky it may be we need to add the ASUS driver too...

Please let us know what your HWIDS are and if you know where we can find the drivers at ASUS a link is considered polite. please start a thread over in the Graphics forum. check my signature for tools and info.

have a great day!

Welcome to DriverPacks, thanks for joining.

sorry, we haven't added support for vista yet.

4,556

(10 replies, posted in Other)

ROFL  - I meant PFC Downey AKA Revampster

Don't ever change, you are excellent sanity maintenance for me... (so i can keep my hair)

now that is somthing very special...

go make her day reflect your appreciation...

4,558

(1 replies, posted in DriverPack Mass Storage)

USB devices are in the Third Party DriverPacks...

You can, and need to, make your own pack...

http://forum.driverpacks.net/viewtopic.php?id=5

4,559

(15 replies, posted in Software)

if you have access to adobe you can OCR that way...

The driver in V4 says 5.1.6000.xxx where old drivers said 5.1.2600.xxx

strange 5.1.6000.xxx  is not valid - it should be 5.1.2600.xxx

there is no NT version 5.1.6000  it's either 2600 for xp, or 3790 for 2K3

4,561

(10 replies, posted in Other)

well I have been learned...

if you need assitance in the hows and the whys
i code base and am very familiar with what is atually done by the base to make it work...

so since i now know that we can't be trusted wink at least i can keep you from pulling your hair out...

oops, forgot you probably lost your hair already - guess i lost my head - tee hee

i belive you are haveing issues because your monitor (your laptop screen)
needs support for non standard resolutions.

It is a wide screen? yes...

i believe you need kb883667

this patch was included in base at one time and i was toying with adding it again...


http://forum.driverpacks.net/viewtopic. … 221#p17221

@Mr_S  i bet you are a good mom... tee hee

4,563

(74 replies, posted in Vista-Tool)

agreed

this is the same driver that VMWare uses so ill be testing this

jaak i think the drivers INF needs the HWID but the mass INI does not...

i could just be tired and confused... ;P

4,566

(15 replies, posted in Other)

Well you have impressed me, so I will elaborate

I use a virtual machine to test before I do anything else.

I use vmware so I need the vmware tools
(the VMWare lines can be omitted if you don't use VMW and if you do 
the install will fail silently if vmware isn't the current environment.
so there is no need to remove them)

with ryanvm integrator;
I add NR_IE7en_Addon_1.0.6b.7z and have no issues with that.
i also add ReapersOODef10Addon.7z

I also use RogueSpears .NET All-In-One Addon  (dotnetaio.exe)
but i don't use ryanvm to install it - see below

from my cmdlines.txt I call runonceex.cmd
which contains the commands

rem runonceex.cmd file
for /f "delims=: tokens=1" %%i in ("%~dp0") do SET drive=%%i:

"%drive%\vmw\VMTools.msi" /quiet /norestart
rem VMware Tools will install if we're in VMware

REGEDIT /S "%drive%\WPI\Install\REG\OO.REG"
rem registers O&O defrag

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY%\996 /V 1 /D "cmd /c start /wait %drive%\WPI\INSTALL\SYSTEM\dotnetaio.exe"
rem   installs .net before we run WPI which is a .NET based app 
rem   so WPI won't crash like it will if we run the .net installer from WPI...

REG ADD %KEY%\996 /V 2 /D "%SystemDrive%\DPsFnshr.exe"
rem ;) driverpacks finisher

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
REG ADD %KEY% /V runtwiceex /D "%drive%\$OEM$\RunTwiceex.cmd"

EXIT
rem runtwiceex.cmd file
rem @ECHO OFF

for /f "delims=: tokens=1" %%i in ("%~dp0") do SET drive=%%i:

"%drive%\WPI\Tools\reschange.exe" -width=1024 -height=768 -force -quiet
rem makes absolutely certain that 1024x768 gets set 
rem (I don't know why this has to be so difficult but it is)

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 3 /D "%drive%\WPI\WPI.hta"
rem   sets wpi to run after the reboot. 

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
REG DELETE %KEY% /V runtwiceex /F
rem  delete the key that called this file making sure runtwice only runs once... (hee hee) 

SHUTDOWN /R /F /T 1
rem   we need to reboot because we just finished installing .net 
rem   and it requires a reboot before we can successfully run WPI.

EXIT

after WPI has run and i reboot my unattended install is completed in VMWare
I then run MSUpdate which provides the missing patches list for Office and Windows.

I download all the missing MS windows patches and integrate them to my UWXP source with nLite.
i download all the missing Office patches and use my script to add them.

its complicated but its bullet proof too. Often people talk about the "time" required. From my perspective if it's Unattended then time is not really an issue is it, I mean you don't have to watch it, or even be there.

Jeff

PS JAVA installs like a dream from WPI
useing RyanVM Sun JRE 6 Update 4 Switchless Installer

as i said almost any program you can think of - somebody has already automated the install

http://tracker.ryanvm.net/ is a good place to start and then check the nLite forums.

PSS i liked the sumation you made - every machine is a master...
and therefore is as clean and up to date as is possable.

now if i had 20 identical machines to load - one master... ghost cast... DONE... no brainer...

please correct me if i have gotten confused on what works and what doesn't
(i dont have this hardware to be able to test myself)

PS i am finaly done editing that post

what version are you useing the version i am looking at does have it

since loading the driver is the problem we DON'T want it to be there

PS i was editing my post when you posted so reread my last
I would be honoured to have your help...

I believe the extended output of the command I gave you will lead us to eventual success with VIA and SI

i also believe "skipping" this driver in the mass INI will give you immediate success.

there are a number of ways to get where we are going.

the easiest is to delete the specific HWID (PCI\VEN_1106&DEV_0591&CC_0101) from the mass INI in the V4 section.
however it is likely the entire series behaves the same way (just a guess)

Or add the following line to the problem VIA sections in DriverPack_MassStorage_wnt5_x86-32.ini

ms_1_exc_skipIfOS="wxp"

example for HWID listed above     PCI\VEN_1106&DEV_0591&CC_0101

[V4]
ms_count=1
ms_1_deviceName="VIA HYPERION SATA IDE"
ms_1_tag="VIBUS"
ms_1_sysFile="VIBUS.SYS"
ms_1_hwids="PCI\VEN_1106&DEV_5372&CC_0101,PCI\VEN_1106&DEV_3149&CC_0101,PCI\VEN_1106&DEV_0591&CC_0101,PCI\VEN_1106&DEV_5337&CC_0101,PCI\VEN_1106&DEV_3349&CC_0101,PCI\VEN_1106&DEV_5287&CC_0101,PCI\VEN_1106&DEV_0581&CC_0101,PCI\VEN_1106&DEV_5324&CC_0101"
ms_1_isBusExtender=true
ms_1_exc_skipIfOS="wxp"

above code will disable this driver in text mode for XP

and this example disables it for 2k, XP and 2K3 (disable text mode and finisher for all supported OS's - PnP will still be supported)

[V4]
ms_count=0
ms_1_deviceName="VIA HYPERION SATA IDE"
ms_1_tag="VIBUS"
ms_1_sysFile="VIBUS.SYS"
ms_1_hwids="PCI\VEN_1106&DEV_5372&CC_0101,PCI\VEN_1106&DEV_3149&CC_0101,PCI\VEN_1106&DEV_0591&CC_0101,PCI\VEN_1106&DEV_5337&CC_0101,PCI\VEN_1106&DEV_3349&CC_0101,PCI\VEN_1106&DEV_5287&CC_0101,PCI\VEN_1106&DEV_0581&CC_0101,PCI\VEN_1106&DEV_5324&CC_0101"
ms_1_isBusExtender=true

which is probably neccessary for a windows install

but I am guessing this will be death for BartPE support of this controller.
someone who has this hardware will need to test and report.

Read before you post... (link in my signature)

4. Don't forget to COPY/PASTE the relevant files INSIDE CODE tags.

ALWAYS include in your post
-DPs_BASE.ini (from the same directory as DPs_BASE.exe)
-DPs_BASE.log (from the same directory as DPs_BASE.exe)

IF RELEVANT, include in your post (in this case it is)
-%SystemRoot%\DPsFnshr.log

same answer as i gave to your other post...

can you please read the read before you post in my signature.

your post doesn't make sense to me.

and you don't have a [BUG]... it might turn out to be a [REQ] after we see your logs.

I removed the [BUG] from your title because the base program itself is not crashing / causeing the error
a bug is a problem with the main executables.

You need to report this to AVG as a false positive.

As you said this has happened before - and was reported and fixed once.

Let us know your progress with them.

the &CC_0101 and the &CC_0104 identify whether to use the RAID or non-RAID version...

the problem seems to be related to non RAID mode emulates IDE (in text mode)
and if the text mode driver is loaded it wont find the device.
(because the MB is lying to the OS and reporting it as standard IDE)

try this; get the hwid tool and use the following command -->
devcon hwids =hdc

post results please!

(you should get somthing like the following)

PCI\VEN_8086&DEV_24D1&SUBSYS_24D11458&REV_02\3&13C0B0C5&0&FA
    Name: Intel(R) 82801EB Ultra ATA Storage Controllers
    Hardware ID's:
        PCI\VEN_8086&DEV_24D1&SUBSYS_24D11458&REV_02
        PCI\VEN_8086&DEV_24D1&SUBSYS_24D11458
        PCI\VEN_8086&DEV_24D1&CC_01018F
        PCI\VEN_8086&DEV_24D1&CC_0101
    Compatible ID's:
        PCI\VEN_8086&DEV_24D1&REV_02
        PCI\VEN_8086&DEV_24D1
        PCI\VEN_8086&CC_01018F
        PCI\VEN_8086&CC_0101
        PCI\VEN_8086
        PCI\CC_01018F
        PCI\CC_0101

this is the actuall list used by windows for matching drivers (top down compare)

it is my GUESS that we need to "skip" this driver for base (non-RAID) mode in the mass storage INI
so the driver doesn't get loaded (during text mode setup) and interfere  with the standard IDE emulation feature of the MB.
(by being seen as a "better" match than the standard IDE driver)

Since the driver is still in the pack it WILL be picked up during the PnP phase of setup

----  I don't think that it is obvious so let me elaborate for the benefit of everyone ----

the mass storage INI only effects text mode setup phase
all drivers in the Mass Storage pack are available to the PnP setup phase - regardless of what is in the mass storage INI.
-- or we could say only mass storage drivers referenced in the INI are added to text mode setup. --

the INI can also be used to call a setup.exe or other support files AFTER and only IF setup installs a device in PnP phase (the "finisher", useing the mass INI, will do this AFTER all devices are installed by setup).

Welcome to DriverPacks, We're Glad your here.

Nice details and info. Always a pleasure to to see a first post done so well!

newsposter wrote:

perhaps it's time to 'split' the mass storage pack into two parts.

A pack being purely non-raid drivers and HWIDs.

B pack being all of the raid stuff and HWIDs.

Jaak attempted this once before he called it his sfx-mini-packs and it was a loser... wink
I helped him with it and like you thought that it had potential...

thanks for the input...  perhaps we may reconsider, but as i said it was tried once.
----------------------------------

@txt3rob
Did you try enableing RAID in bios?