Search options (Page 1 of 2)

Thanks again OverFlow,

for verrry clear instruction(s) and everything.

Now I can sleep happly without anything left in mind.

Thanks OverFlow , Thanks mr_smartepants

also keep in mind to check missing (not replaced)
PCI\VEN_1000&DEV_0012&SUBSYS_001b0e11 = "sym_hi"
PCI\VEN_1000&DEV_000b&SUBSYS_60040e11 = "sym_hi"
entries too
(maybe they are not required anymore, but better a 2nd check made by you guys to be sure ....  , well I am pretty sure you will make a clean check....)

All Credits to Olegpov, who catched missing hwids with his well known sharpe eagle eyes.
And thanks to JonF and Saydin77,
We had some days of confusions since JonF figured out things 18-Jan , I am very happy now everything related will be back to normal.

Overall,
THANKS TO GREAT DP TEAM.

I do not think any bug report for bartpe or anyone asking why new unused files on windows cd since both will work on the field nicely.
I understand (agree , fine.....) your decision not updating dps_base, not urgent at all.

YES,
Your explanations %500 cleared all confusions and shines our way ,
Thanks a loooot for Strong Support.

Hi OverFlow,

thanks for all clear replies (specially to post 3)

just to verify:
so CPQ32FS2.SYS file copied with names SYMC8XX.SYS , SYMC810.SYS , SYM_HI.SYS to overcome 1 driver instead of 3 native driver issue, instead same file with 3 names . Can you confirm this is intentional ?
(also re-tested with untouched pebuilder311a , DPs_BASE_1006 , DP_MassStorage_wnt5_x86-32_1101)

some comments about things on this topic:
yes, pebuilder is best reference, since it is stable , trustable, and great work of Bart Lagerweij which shows his accurate far sight I admire a lot.
Heh, comparing with winbuilder, winbuilder have oppositely famous with its unstable and untrustability, but sadly for today it is what many have at hand.
(I hope one day a good programmer provide a better pe-build-scripting tool, hope never ends )
anyway,
we, nt5x fans, want more
I am making pe1x64 builds since ~2009-10 along with multi language support (chinese etc.) already integrating some custom x64 drivers but sadly we do not have a mass storage package for today.
Is there any hope (take this as a honest request) to have DP_MassStorage_wnt5_x64..... one day, which I believe increase popularity of both pe1x64 and xpx64 .

Hi Mr.Cyrix

Kare very recently changed the distribution method,
For BartPE plugin email Kare
http://www.kare-net.de/impressum-e.html

A new Version of "Driver Import PE" is available.
The current DIPE have more compatibility and any bug fixes.

Driver Import PE V1.3.2.7
-------------------------------------
- manuell mode: driver detection bug fixed
- Hover Buttons added
- .mof-Support integrated
- Info Button added
- DriverPacks - Foldercheck integrated
- Subdriver detection bug fixed
- Reduce Memory Function added.
- Driver Installer enhanced , (e.g. Nvidia Nforce Network and all exotic Driver)
- Read Data (class)-bug fixed

the bartpe plugin get download on website:
http://www.kare-net.de/plugins-e.html

Also available within LiveXP

New Version of "Driver Import PE" is now downloadable from kare's website
You can get  Driver Import PE pebuilder plugin (BartPE, UBCD4win, XPE, SherpyaXPE, ...) from: http://www.kare-net.de/Plugins.htm

LiveXP users can get updated version by simply downloading new script from LiveXP server. (Click download on winbuilder)

Driver Import PE V1.3.1.8 New features:
--------------------------------
- support to drivers that use "Program Files" folder added (%programfiles%)
- filename renamed DrvImp.exe to DrvImpe.exe
- check subdriver on manual inf import (ex: hdaudio)
- Driver check (manual) os type, (When "System (OS) on HD" method selected, you see hostoses names on disk(s))
- Coinstaller improved (sigmatel audio devices works properly)
- Driver searchengine 12% faster
- hardware detection bug fixed
- Note for frequently asked Nvidia Lan drivers: with "System (OS) on HDD" method you can install at once. With "Folder inf" method you should first install bus driver than maindriver.

Overflow:

yep i think as you write too, i guess dipe will delete reboot line before installing to hostospe.

Thanks for concern

Special thanks to galapo, as usual

YES Galapo,

Changing DP JRAID_I.inf [JM] section:
CopyFiles=JRAID.Copy
Reboot

to

CopyFiles=JRAID.Copy
Addreg=Inst.AddReg

makes it work
Also i noticed xraid_f.inf have same line too, so i change with same method and it worked too. When dipe searches in package, it first finds JRAID_I.inf than xraid_f.inf, both working with this fix and i guess makes the same thing. Only with xraid_f.inf it writes "GIGABYTE GBB36X Controller" on the screen.

Anyway, now question is what is next step???
I made a rough seach, and there are about 53 .inf files that have REBOOT line
IS dipe change reboot lines with Addreg=Inst.AddReg before adding driver to hostos appropriate?????
or what is the appropriate method???

ps: Kare reads this topic regularly.

ps: Out of topic: Galapo, Maybe that is the reason of my failure when trying "Off Line SysPrep Tool" looong time ago.

yes, of course UBCD4Win , i wrote in the begining but forgot in the middle , i know both, i like UBCD4Win more

Goodluck with trial

"as i said i tried it in vmware and it reported failure"

?! you should report this to boot-land
http://www.boot-land.net/forums/index.php?showforum=52

i frequently make builds with livexp and try with vmware, no problem.