I second the motion!
Done...
Welcome to the team Mooms
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
I second the motion!
Done...
Welcome to the team Mooms
Hey Galapo,
I was hoping somebody would save me from drowning!
Thanks!
I did not know that OLSP would work from windows too...
thinking, very cool... a machine with two hard drives w/bios select boot device...
that could be slick. its the workhorse and the source and deployment tester in one
So the !put 'DriverPacks-MassStorage' folder here! instruction refers to copying them from DriverPacks BASE generated BartPE plugin folder...
I see there is a whole paragraph on this in your instructions and you link to my BartPE tutorial too (blushes)
i found the OfflineSysPrep.htm file in the same folder as !put...
Maybe it would be better to be named OfflineSysPrep-Instructions_En.htm or even ReadMe.htm LOL
Thanks again for stopping by
You're a DriverPacks hero!
I think i know what the problem is... but don't quote me since I'm just guessing.
(I just don't have the time to waste torchering myself like you crazy sysprep guys.)
I don't see anywhere in the directions where is says anything about extracting a mass storage pack??? (so why did you?)
I believe you are trying to make it harder than it is. by shooting yourself in the foot right out of the chute.
let offline sysprep stage mass storage...
Don't do anything manually and don't add your drivers (KISS method)
follow the directions to the letter FIRST... then experiment
I can explain this in excruciating detail but lets keep it simple
- Galapo does not use the drivers in the pack. (at least not in their raw state as they exist in the pack)
- DriverPacks BASE has a feature to create a BartPE MS plugin from our DriverPack MassStorage pack...
the generated plugin folder is remarkably different than what is in the DriverPack MassStorage archive
the pack and the plugin cannot coexist (they overlap in a cataclysmic fashion - Since providers can not write drivers correctly))
- If you mess with the delicate balance of drivers=hwids at all after OLSP you absolutely will cause failure
(don't extract DriverPack MassStorage and don't do anything else with it either... or you are going to be fighting with this forever)
(don't add your own mass drivers or any DriverPacks packs or sysprep BSMD or ANYTHING else) It is also very likely that your home made driverpack is causing a conflict and cascaded failure with mass storage (get your source working with just mass, then play with adding your drivers back. Or alternately you could simply use our DriverPacks.
HINT:
NEVER EVER give your root driver folder a name longer than one character.
hint, hint, it has something to do with exceeding max path lengths. IE 100 subfolders now each one has an additional say 15 extranious letters, 1500 characters burned out of your precious maximum of 2048. Same senario with a single letter folder. 100 x 1 100 thus we have saved 1400 bytes we can now use for more driver folders to search. so don't name your root folder \DRIVERS THis costs you 6 X (the number of subfolders you have in /drivers/) = X > more than > if you use just \D\
Theory...
1 Offline sysprep stages drivers correctly...
2 you add extracted DriverPack MassStorage to search path
result over 2000 duplicated HWIDS and hundreds of duplicate file names (last file written wins!)
- SysPrep can not handle conflicting HWIDs Not even a single duplicate is tolerated (same for file names)
Shot yourself in the foot.
3 you add your pack
result adding hundreds or even thousands of additional HWID conflicts.
End result
Machine won't boot (ever)
Look, if it were easy (that somone could just dump a bunch of drivers into a folder and it would then work) we would not get a million downloads a week
We pool our recources and our diverse range of experience here and at our sister sites like 911 and UBCD4Win and MSFN and SiginetSoftware etc...
so that all our lifes can be easier... no need to 'reinvent the wheel', just ask and whe will find you a wheel in exactly your size
Not all the drivers in the mass storage pack are sysprep compatible, some aren't even xp compatible.
That is why Galapo uses the output of my BartPE Plugin for slipstreaming the mass drivers
In this way only the platform appropriate drivers are selected and used... instead of the entire pack.
the output of Kickarse tool is not meant to be used in its entirety... it is to be used to pick and choose from .
There is also a memory limit with xp on how many drivers you can load. You can get around this limit by using the ntldr from higher os's, but i don't think this is legal.
Please note bigfoot's point, SysPrep only allows for half the resources supported during normal setup... 2048 instead of 4096.
It is definately a copyrite violation to use ntldr from 2k3 server. Unless you dedicate a 2k3 license for this. (Like BartPE, license the disc /install)
Although some users ventured into what is/was arguably a grey area both useing the Longhorn ntldr when it was available as a free 180 day evaluation version and by useing the version included in service packs. (It has never taken 180 days to install XP to my knowlege) If you have site licensing then you could simply burn an extra license
the key here is...
AHCI is not a windows function it is a driver function.
Please realize that there are often two drivers for each device...
One for each mode... and each mode will report a different set of HWIDs
Try it for yourself. Run the hwids tool on your machine in both modes and compare the RAID section at bottom - compatable IDs
Please also note that if you switch from RAID to non-RAID or from non-RAID to RAID then the drive must be formatted in order to be used
so if a device is not supported when it is set in a particular mode...
it simply means
we do not have that driver or
we have the wrong version or
we are missing a HWID or
we have a conflict...
Give us the HWIDs of the device (using the tool in my signature AND when it is set to AHCI mode) and we will fix it in the pack This of course not only fixes it for you but for everyone else too.
PS the reason you found no info on AHCI w/XP problems on the DriverPacks forum is because there are none.
It is simply a driver issue... One we deal with all the time
I am not entirely convinced that a drive will perform faster in everyday use based on its mode...
A particular drive is simply as fast as it is you want faster drive access? Buy a faster drive!
the most valid reason to want AHCI is to hotswap drives... again not an everyday use item
thank you. I wanted to make sure it was not related to the Bug that exists when all packs (including all 3rd party DriverPack)) were used
HWIDs please?
Welcome to DriverPacks HilcrRWise
Galapo's OffLine SysPrep is the preferred and by far the best method to add DriverPack MassStorage. (sticky in this forum)
It also has features for HAL and other SysPrep related functions.
Don't use KTD... it is depreciated and flawed (makepnf causes lots of issues)... Use the SAD feature of DriverPacks BASE instead
Hint:
Open the DP_Inst_Tool.cmd REM the lines that call the dpinst.exe and DriverPacks Finisher
Run the modded tool.cmd. This will stage the drivers and seed the devpath entry in the registry.
(be sure not to run the finisher as it will delete / cleanup / remove everything .)
Optional run 'DPInst.exe /c /s /sh /lm /el /sa' in runonce or runonceex so it will run after deployment
Add a call to the DriverPacks Finisher in runonce or runonceex so it will run after deployment and clean up / remove all unused drivers
Have a great day!
LOL...
A win is a win...
we have DriverVer=11/08/2005, 2.06.0.311
your link is also for DriverVer=11/08/2005, 2.06.0.311
so it seems to be the same version we already have...
We will leave the REQ open so that the Packs INI gets updated!
and since you have already tested it ...
Hi Friends,
One more thing about driver packs that i was also unable to install modem in one of my laptop (Conhexant). Any solution for that...????
check the 3rd party DriverPack forum for modem and monitor and other peripheral device support
http://forum.driverpacks.net/viewforum.php?id=13
that should work...
however if we are missing support for particular device lets report it so we can get it added to DriverPack MassStorage
#2 was very important... tested with win 2k3 sp2 and not working
the download link is to a driver you have tested and is known good?
(obviously better, but not a show stopper )
Let's upgrade this to a [REQ]uest!
Thanks for the feedback it makes the DriverPacks better for everyone!!!
have an awesome day
Jeff
PS added code tags for you
you are seemingly correct...
That Driver is for 2k and XP only, (its specifically excluded for windows 2k3) skipIfOS="w2k3"
Without the full HWIDs of the unit I can't be 100% sure if it is supported by another driver / section / folder
PCI\VEN_105A&DEV_3519 is a generic ID
a more detailed HWID output may be helpful
- see HWIDS tool in my signature
Do you have this hardware?
Have you tested it and know that it fails?
Is this card natively supported by win2k3? (PCI\VEN_105A&DEV_3519 is not)
can you please post a link to a driver that you know does work for 2k3 on this hardware
Can you test a pack if it is added? (assuming it is not natively supported with a variant of the HWID)
Jaak used to say "please help us to help you"...
So... I say to you what Jaak would say
Well done Mulgie!
were you useing any Third Party DriverPacks?
I belive that install from USB uses winnt32.exe instead of setup.exe...
the main DriverPacks and 3rd party DriverPack will not work with winnt32 based installs.
You can use SAD (check the FAQ forum)
If you use DriverPacks BASE to add the mass storage text mode drivers that should work (text mode only!)
The better (and simpler for a noob) way to do this for a one off machine is to use nLite
http://www.nliteos.com/
have a nice day and welcome to DriverPacks
Yes it is possable...
Yes that is what DriverPack MassStorage is aimed at...
and there is more than one good way to do it...
BSMD is not one of them... I could write several pages on why this is the case... please don't make me.
OffLine SysPrep is the best, easiest, most versital way to add DriverPack MassStorage to a sysprep image...
if you go that route 999 out of 1000 machines HDD controlers will be recognized.
(when you trip over machine 1000 let us know and we will add that driver to DriverPack MassStorage too! )
it will simplify some of the process you are doing and eliminate many of the issues you are or may be having completely, reboot loops and with HAL selection and and and...
Please...
http://forum.driverpacks.net/viewtopic. … 147#p32147
http://www.911cd.net/forums//index.php?showtopic=22064
I would try that first... on a clean image
forget other drivers, as you said, and any other post deploy routines, and add them back later.
I think you will be pleasantly surprized after a few successful tests.
If you poke around a little you will find i am not a fan of sysprep at all, But we have several dozen hard core SysPrep gurus on the team... if you get stuck one of them will step in here and save you, I promise!
Jeff
PS We are here so you don't have to maintain your own driver repository
Um...
1 One of the hard working, dedicated, motivated, respected, and highly talented DriverPacks team members will add this driver
2 That individual will very likely request you to test the latest RC version that they belive includes support for this device
Mass storage is currently being worked on by a couple of guys who have been on the testing team a long time and are getting thier feet wet with it, and JakeLD who has taken over for Jaak as our Mass Storage Pack guru. We are in our sixth revision just this month so it probably won't be long ...
Jeff
nothing installed at all...
Logs please!
The reason for Sound is not as logical... LOL
the sound drivers are just huge . (period)
we just try and keep the size balanced
We just switched to a new homepage... Drupal based... On the old site we had an "Overview page" that i just discovered did not make it to the new site. Yikes! I will Email Wim to see about what happened to it. (Perhaps I just can't find it! lol)
Welcome to DriverPacks,
and have a great day!
Skip the BSMD...
if you slipstream the mass drivers the Text Mode drivers will behave as if included by MS themselves No further action is required. Aside from setting hdd controler type to standard before your last shutdown to image.
The preferred method of doing this is to use Galapo's OffLine SysPrep...
Because of the PnP drivers
DriverPacks BASE method would require the additional step of SAD (Stand Alone Drivers, for software first installs) for the PnP drivers
Advantage - all packs can be run against the target and all hardware will be updated with current drivers
or you could include the mass pack with your step 2.
OffLine SysPrep will include both text mode and PnP mass storage drivers
Advantage OLSP will add registry settings to the Hive to address some reported issues that DriverPacks BASE does not address (edge cases).
OLSP is specificaly designed to be used for sysprep
a combination is best... OLSP then SAD M2
(SAD M2 Replaces step two in your example)
Moving this to the proper forum
org = DriverPack MassStorage
target = Universal imaging
Please take a moment to review the over five years of Q and A contained here in the UI forum...
There is a wealth of experience and knowledge.
Welcome to DriverPacks.net
Have a great day!
Thanks for confirming!
soundblaster 16 and 32 are natively supported... the 64 is not included
Broderbund - Prince of persia (original) was one of my all time favorites -
I still make sure to get all of the PoP releases as a result
Speaking of New versions of old games... Wolfenstein 2009 is excellent!!!
*CTL00?? does not return a hit in the packs...
creative driver
; Date : 25th Jun '97
; Revision : 1.01
supports these hwids
[Creative]
;
; NOTE: We omit hardware IDs for each of these devices, so that the user will
; be able to supply an OEM-supplied driver with fuller functionality at
; the "Found New Hardware" popup.
;
%*CTL0001.DeviceDesc%=CTL0001_Device, *CTL0001
%*CTL0001.DeviceDesc%=CTL0001_Device, *CTL0031
%*CTL0001.DeviceDesc%=CTL0001_Device, *CTL0041
%*CTL0042.DeviceDesc%=CTL0001_Device, *CTL0042
%*CTL0001.DeviceDesc%=CTL0001_Device, *CTL0043
%*CTL0044.DeviceDesc%=CTL0001_Device, *CTL0044
%*CTL0042.DeviceDesc%=CTL0001_Device, *CTL0045
%*CTL0046.DeviceDesc%=CTL0001_Device, *CTL0046
%*CTL0001.DeviceDesc%=CTL0001_Device, *CTL0047
%*CTL0021.DeviceDesc%=CTL0021_Device, *CTL0021
%*CTL0021.DeviceDesc%=CTL0021_Device, *CTL8001
%*CTL0022.DeviceDesc%=CTL0021_Device, *CTL0022
%*CTL0023.DeviceDesc%=CTL0021_Device, *CTL0023
%*CTL0024.DeviceDesc%=CTL0021_Device, *CTL0024
%*CTL0051.DeviceDesc%=CTL0051_Device, *CTL0051
%*CTL7FFF.DeviceDesc%=CTL7FFF_Device, *CTL7FFF
; hardware ID for all the joyport
%*PNPB02F.DeviceDesc%=MSJSTICK, *CTL7001
%*PNPB02F.DeviceDesc%=MSJSTICK, *CTL7002
%*PNPB02F.DeviceDesc%=MSJSTICK, *CTL7005
I have this card in my 486... it just won't die.
I built it back in 98
DFI-MB - 4 x PCI, 3 x ISA, 1 x VLB
AMD CPU am5x86-p75-s 133Mhz (overclocked to 160Mhz for over 10 years now)
Fancy cpu cooler with a thermal electric conductor
The the cpu allways stays ICE cold to the touch, (the edges are exposed) but don't touch that heatsink when checking!
64MB Ram
BusLogic Caching Controller card VLB, 4 x IDE w/16MB RAM (It has its own dedicated I386 cpu on board )
I bought the MB with legacy support for VLB so I could keep this card...
man it was fast I could duplicate a full 850MB drive in under 15 min
ISA Intel NIC 100Mb
PCI TV Tuner Card
PCI adaptec Wide SCSI adapter
Floppy; 3.5 1.44, 5.25 1.2, QIC Colorado T1000 Backup
IDE 40x CD ROM
IDE HDDs usually four, one striped set for OS internal / Two removable drive trays for data
SCSI 3 x Nakamichi MBR-7 7 Disc CD changers 2x - These are awesome pieces of hardware...
Great for a jukebox Sound quality and THD is Excellent, however burning 21 drive letters created issues occasionaly
Soundblaster Awe64
Hooked to my Sansui 9090 DB 125 Watts per channel RMS (500 watts)
At a lan party at my house i turned it on when nobody was looking
I then fired my shotgun
There was not a clean pair of shorts in the house LOL Hee hee ho ho
courier v.everything 33.6 - Dialup... those were the days!
The Kids use it as a media center, tv radio CDs etc...
I am just in disbelief that it still runs...
I have brutalized this machine in every possable way for a decade
I guess i build machines to well... sorry
Quake was the nail in this machines coffin...
It was as fast as or faster than any pentium 166/200 machine,
until someone wrote an app (Quake) that took advantage of the pentium specific instruction codes.
At that point it just suffered to much of a performance disadvantage and was retired to TV and CD player status...
It also still serves as a DOS, win 3.11, win95/98 reference (well yeah its multiboot )
Ah the memorys...
Sadly no it is not supported... but that was fun anyway!
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.330 seconds, 5 queries executed ]