2,376

(8 replies, posted in DriverPack Mass Storage)

Many times the recovery / reinstall Disc will have XP drivers on it along with the Vista ones smile

Please verify it is not a conflict with antivirus or firewall software
One of the Google hits indicated possible conflict with a Logitech mouse and some USB keyboards. (Docking station?)
IE try and eliminate possible irritations to the Mass storage driver.
Hint: check device manager for the IRQ List "view Devices by Connection" smile
Who is Sharing the Interrupt with the Mass Controller?
is the machine in APIC mode?

since it seems to be an interrupt conflict the thing that is stomping on the Mass Storage's IRQ is probably as much to blame
as the mass driver.

- its a conflict in the interaction of TWO (or more) hardware devices that are not sharing the same IRQ nicely wink

  - That is why there are so few posts on this,
     It is The Unique combo of hardware and settings...
     Your specific model of PC, and your specific combo of drivers & other installed software.
     and possibly some bad luck when the machine enumerated the IRQs.
      - it may be that forcing the machine to re-enumerate may eliminate the problem too.
     
Updating the other device(s) that share(s) the IRQ with your Mass Storage driver may also fix your issue
try the actual chipset OEMs Intel Nvidia blah blaa blah... we may be out of date wink

If you post the fix here and it is driver related (probably a driver... but perhaps not Iastor)
we may be able to implement it in a future DriverPacks release wink
(you would of course get full credit wink)

PS (tech / training time is billable wink tongue )
your homework is to report back LOL

2,377

(2 replies, posted in Windows 7 Discussion)

I don't have access to it sad
just showing 7077 on msdn for me

2,378

(8 replies, posted in DriverPack Mass Storage)

I jsut did it and it showed a full page

http://forum.driverpacks.net/search.php

2,379

(8 replies, posted in DriverPack Mass Storage)

well first off try Googleing irql_not_less_or_equal iastor.sys

Second it may be that the reference driver will not work on that particuar laptop, try the one from the OEM (Acer).

It could also be something besides the iastor driver... something that is crashing that driver...

Apparently lots of dell owners are having that issue too... first time it has been reported here...

it seems like you have a handle on the basics....

let's explore a little deeper...

during windows setup M1...
M1 has a path limit of 4096 (way light of what DriverPacks needs)
M1 uses the suggested MS path method - in winnt.sif
M1 extracts the 7zip archives and cab compresses the drivers.
Since windows natively supports cabbed drivers...
Simply haveing them on the CD/DVD (ODD) enables the manual option of "Search removable media" wink

  with SAD M1...
  Most of the time Search removable media will be all you need, 
  search the ODD once and be done.

During windows setup or SAD with M2...
M2 uses the registry entry for the devicepath, allowing for a great deal more entries than M1 / winnt.sif
7zip gives better compression than Cabbing - but must be extracted before use wink
M2 will allow for all connected hardware to be detected and drivers installed properly during setup.

  With SAD M2
  drivers are extracted to the HDD first then runs DPInst.exe then runs the finisher.


If you had either a M1 OR M2 disc with you i would simply run DP_Inst_tool
Since doing that will update all the drivers, not just the missing ones wink
and if there are any known issues with the drivers then the finisher will address them wink

KTD does not call the finisher so some drivers may not install properly (video and audio mostly)

np
1 use dpbase slipstream mass storage and all main packs with M2 no KTD
2 create a SAD M1 folder copy to HDD after install, run devpath to set the KTD path...

this is pretty well outlined and asked and answered in the other thread...

Cant make it any easier than that

I would like to State again KTD  Most of the time  is a waste of disk space,
because If you are installing hardware you are going to be at the machine anyway...
It is always desirable to check for a better driver at the time of the hardware install.

are you trying to create a universal image?

A better method for you would be to use SAD after the upgrade wink...

Don't use a DriverPacks modified source for repair / upgrade.

If i am remembering correctly upgrade uses winnt32.exe which is not supported currently by DriverPacks...

Reading the stickys in this forum is a good start wink

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

Useing 'custom' instead of guirunonce is better for attended installs wink
- You will need to call the finisher manually / yourself with the 'custom' method

your info does not make sense... I refuse to belive your DVD is your C: drive... ???
                                         \/
"2. receive an error "INF file c:\XPSP3\i386\TXTSETUP.sif contains a syntax error."

It looks as though you called the setup from your HDD not the DVD...

I am 99% sure that is why you failed big_smile

Run it from an ODD (Optical Disc Drive, CD/DVD) and report back

Welcome to DriverPacks vfclists.

- I am the Admin - wink

We don't include vista drivers wink... big_smile

The reason it takes longer is all of the included mass storage drivers will be loaded into RAM...
Whether they are needed or not... this is by MS design.

It is better to wait a minute and know your HDD will be found,
than to have to keep editing and reburning new PE Disks all the time wink

Remember BartPE is a recovery tool not an OS replacement...
the most important component of a recovery tool is the one that ensures that the HDD's are found big_smile

Jeff

I am not surprized you did not find any documentation on this since
DriverPacks does not support attended installations... (Like a repair or upgrade install)

Other people ARE doing this though... it should work wink - But it is not supported by DriverPacks.

Welcome to DriverPacks.net

jeff

Excellent Info Muiz

Thank You...

Wont it be prudent to keep the vista and win7 drivers together...
except maybe the ati. that you said fails if you don't remove the win7 sections?

2,389

(35 replies, posted in Windows 7 Discussion)

200 gig lol

according to Tom's hardware info / testing with Vista there's not much performance gain after 3 gig...

but it does give me crazy thoughts like installing a VM to a ramdisk wink and picking a sweet snapshot big_smile

2,390

(35 replies, posted in Windows 7 Discussion)

Agreed
it is more of an extension of 'run program in compatibility mode'
- the "VM" would actually be running real-time as a component of Win7. Not in a window as a separate shell.

It's Brilliant really... If it works then any corporate objections to upgrading cease to be an issue.
XP could successfully be phased out.

Yes we know how to add a favicon...

I do websites for a living wink... silly boy tongue
(
click on the website link below my avitar
- Or search for Rolls-Royce Service big_smile
- Note the favicon wink
- [ I like Sam wink ] -
)

However it is required to have root access to the file system... ONLY Bâshrat the Sneaky has root access to DriverPacks.net big_smile

2,392

(35 replies, posted in Windows 7 Discussion)

Now That is something to get excited about...

And it address' the issues of our corporate clients that are deeply entrenched with XP specific apps...

Well done MS.

KTD has some known issues... please let us know how it works out...

2,394

(30 replies, posted in DriverPack CPU)

No feedback is desirable...

I have yet t recieve feedback on my mass storage driverpack plugin for BartPE a year ago.

Millions of people are useing it - 0 feedback.

Nobody ever says thank you - or It works Great!

People by nature only want to bitch.... they never post when they are happy...


No feedBack Means it is working perfectly wink

2,395

(2 replies, posted in Other)

agreed


Don't remove native drivers with Nlite or other methods

2,396

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

ROFL...

Well yeah... It would seem so!

there should be a master list maitained by our resident 3rd party DriverPack master Twig123...

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

the 3rd party DriverPack is YOUR forum you can help clean it up too smile tongue big_smile

Glad to see you active on the board it seems you are one of our silent veterans wink

Jeff

2,398

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

I got called on the carpet for my closing statement above in a Very Nice and Well Worded e-mail...

I received a link to here http://www.ee.oulu.fi/research/ouspg/pr … 0/archive/
Apparently this was all started by a a college research paper that displays the POTENTIAL to exploit many archive programs like 7zip and many others.

i wish to publicly apologize, and withdraw the word 'rumor'. Since it is actually based on a published Thesis paper at a University.

that just leaves us with unsubstantiated  smile  tongue  LOL (Show me a link to a SARC report or similar)

Don't ever hesitate to post a 'heads up' to a problem we may have - or potentialy could have.
We do want to know!

At this time there is just nothing for us to worry about since no known exploits actually exist in the wild big_smile
Once an exploit was exposed we could then evaluate any potential exposure from a bootable ROM (DVD) (probably NIL)
(it is usually at this point one of my fellow team members will shoot me down LOL)

I admire your persistence and professionalism Xabib... I hope we see more of you in the future~

Have a great day and please accept our warm welcome.

2,399

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

yeah... we get reports every other month about Mute.exe too...
But it is the AV vendor(s) not the mute.exe app that is the problem wink

usually it is AVG
(they are absolutely the worst AV - if your rating is based on the reporting of false positives)
- if i had a dollar for every false positive reported here i would be rich smile

Again, Thank YOU 
It is better to be safe than sorry...

you should just be able to google the KB numbers wink

Google KB943545