76 Reply by OverFlow

(525 replies, posted in Windows 7 tools)

mizar11 wrote:
OverFlow wrote:

No. Just got distracted.  tongue

DO NOT DO THIS ON OPTICAL MEDIA...
for thumb drive or better. All drivers extracted (M1 or M3)

create folder on the root of your thumb drive called "OEM"

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET THUMBDRIVE=%%i:& GOTO DPsFound
:DPsFound

Start /wait /high /separate "" %THUMBDRIVE%\OEM\dp_install_tool.CMD


EXIT

that should solve your issue.

= Since M1 (or M3) source is not deleted or extracted or copied it runs much faster (except on ODD devices) this solves two issues for you. The file copy / extraction and the removal of the D drive.

Hi OverFlow,
Thanks for your time, hope you'll have patience with me... I'm not sure to have clearly understood: I have to make a folder in my pen drive root directory, and put inside a new file called dp_install_tool.cmd containing instruction you wrote above. Is it correct? And what about the dp_install_tool.cmd existing in the sources\$OEM$\$1\D\SAD3 directory? Have I to delete it? And about setupcomplete.cmd file, in the sources\%OEM%\$$\Setup\scripts folder? What have I to do with these 2 files? I ask you that because I tried to keep everything original, just joining new dp_install_tool.cmd file in the root OEM folder, and install it from a pen drive on a virtual machine. But nothing happened... sad Hope you'll understand me, I know my english is very bad...
Thank you again for you kindness

I like quote pyramids...

Move the dp_install tool folder FROM the sources\$OEM$\$1\ TO the root OEM folder. Like
ThumbDrive:\OEM\DriverPacks.here.please\D

Leave setupcomplete.cmd where it is and add the code above to it so...

{Win7-Disc source folder}\sources\$oem$\$$\Setup\scripts\setupcomplete.cmd

contains

REM echo off

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET THUMBDRIVE=%%i:& GOTO DPsFound
:DPsFound
Start /wait /high /separate "" %THUMBDRIVE%\OEM\dp_install_tool.CMD /s

REM START %systemdrive%\D\SAD2\DP_Install_Tool.cmd /s

EXIT

See how that goes...

Go to forum: Windows 7 tools

77 Reply by OverFlow

(1 replies, posted in Vista / 7 DriverPack WLAN)

Thanks cheche !

Go to forum: Vista / 7 DriverPack WLAN

78 Reply by OverFlow

(14 replies, posted in Windows 7 Discussion)

TechDud wrote:

[off-topic]

Roughly estimating that if each unit averages 32W over one year for a total average draw of 32kW and at a hypothetical commercial rate of twenty cents per kilowatt*hour, that could add to an annual cost of $12,288 to run 1000 machines 8hrs per day, seven days a week, 240 days per year.

Accessories, such as monitors (or taxes, etc.) are excluded for the rough estimate.
  It also assumes that less than half, perhaps even much less, are in use at once.

[/off-topic]

1.2 Jigawatts! where are we going to get that kind of power?

Go to forum: Windows 7 Discussion

79 Reply by OverFlow

(14 replies, posted in Windows 7 Discussion)

Yes

Go to forum: Windows 7 Discussion

80 Reply by OverFlow

(3 replies, posted in Feature Requests)

LOL I can wave a magic wand over your account if you really want me too tongue.

I could just delete this thread instead big_smile.
I have to wonder if that sets your post count back to zero, or if you would still have 2 posts that just don't exist?

Welcome to DriverPacks !

Go to forum: Feature Requests

81 Reply by OverFlow

(3 replies, posted in Feature Requests)

We have an amazing feature here at DriverPacks.net it's called search... try it sometime.
We show no patience for those who cannot help themselves. (IE use search)
Please note the second stickied topic in this forum http://forum.driverpacks.net/viewforum.php?id=2


NO 64bit support for XP at all. Not now not ever. XP 64 was a joke at best.
If you want 64 bit OS then get an actual working unit (Vista or better)

Go to forum: Feature Requests

82 Reply by OverFlow

(525 replies, posted in Windows 7 tools)

No. Just got distracted.  tongue

DO NOT DO THIS ON OPTICAL MEDIA...
for thumb drive or better. All drivers extracted (M1 or M3)

create folder on the root of your thumb drive called "OEM"

SET TAGFILE=\OEM
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET THUMBDRIVE=%%i:& GOTO DPsFound
:DPsFound

Start /wait /high /separate "" %THUMBDRIVE%\OEM\dp_install_tool.CMD


EXIT

that should solve your issue.

= Since M1 (or M3) source is not deleted or extracted or copied it runs much faster (except on ODD devices) this solves two issues for you. The file copy / extraction and the removal of the D drive.

Go to forum: Windows 7 tools

83 Reply by OverFlow

(294 replies, posted in DriverPack Mass Storage)

HWIDs please

how are you building your BartPE  (UBCD4win) ?

Does version DP_MassStorage_wnt5_x86-32_1209.7z work for you?

Go to forum: DriverPack Mass Storage

84 Reply by OverFlow

(525 replies, posted in Windows 7 tools)

Welcome to DriverPacks.net.

Thank you for the kind words. I think you may have missed something that most of us either think is obvious, or at least well known. the way the tool works is; it sets a RunOnce registry command to delete the folder when the computer is next rebooted. If you haven't rebooted the computer before checking for the "D" folder. There is a very high probability that it WILL still be there... Since it is not supposed to be deleted until the First Reboot AFTER the tool runs. Again this is often missed or not known. Sometimes users overwrite or erase the RunOnce command by accident. The reason is simple it gets around any issues of files that may or may not still be in use tongue.

Please reboot the target machine before verifying whether or not that the cleanup is complete.

Report your results. Hope I guessed correctly.

PS please don't wait 6 months to ask, someone here prolly already knows the answer. big_smile

Go to forum: Windows 7 tools

85 Reply by OverFlow

(3 replies, posted in Windows 7 Discussion)

write a script to search the drives for the SAD folder...

or use search and find several excellent examples posted around here wink

Go to forum: Windows 7 Discussion

86 Reply by OverFlow

(3 replies, posted in Windows 7 Discussion)

/$OEM$/1$/   

is a direct instruction to copy to disc...
this link describes the meanings of the OEM folders (it's for XP but you will get the idea)
http://unattended.msfn.org/unattended.xp/view/web/18/


Launch SAD3 directly from the USB drive (not in a $OEM$ folder) and it won't copy them.

Welcome to DriverPacks.net

Go to forum: Windows 7 Discussion

87 Reply by OverFlow

(1 replies, posted in Hardware)

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

Go to forum: Hardware

88 Reply by OverFlow

(1 replies, posted in Feature Requests)

unfortunately we don't have anyone actively updating the packs ATM.

that can change at any time, volunteers maintain them. We never know who or when we will have help.

We are keeping the lights on... it's just a matter of time. big_smile

Go to forum: Feature Requests

89 Reply by OverFlow

(3 replies, posted in Other)

I added you to the testing team.

Welcome to the DriverPacks team!

you should find some new forums to read. See if anything looks like something you want to tackle.

let me know if you have questions

Jeff

Go to forum: Other

90 Reply by OverFlow

(3 replies, posted in Other)

Nope. The project is alive. We just don't have the man power we once did.

it's hard to get people to volunteer.

Go to forum: Other

91 Reply by OverFlow

(12 replies, posted in Windows 8 Discussion)

unfortunately nobody is volunteering to update the packs...

we have always had the saying "help us to help you" , well good help is hard to find big_smile

Jeff

Go to forum: Windows 8 Discussion

92 Reply by OverFlow

(5 replies, posted in Windows 7 Discussion)

We are friends with the guys who develop driverpack solution, however, we do not support their software.

IDK why, perhaps they do?

Go to forum: Windows 7 Discussion

93 Reply by OverFlow

(5 replies, posted in Windows 7 Discussion)

Sure let me summarize our last 12 years of collective coding (hundreds of thousands of lines) in a few sentences so that you will have the complete and thorough understanding required to duplicate our decade of work predicated on a dozen years of experience and user feedback. Once i get that together i'm sure it will only take you mere months to pound out an alpha, at which point you can start getting some user feedback about the hundreds and thousands of exceptions to the rules. how the packs are laid out and the mutual conventions we all depend on.

BRB

can you tell me working mechanism in Timex. I need make watch. hmm

Go to forum: Windows 7 Discussion

94 Reply by OverFlow

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

in the DPs_BASE.ini disable gui and enable all drivers run program... wink

Go to forum: Feedback and Support - DriverPacks Base

95 Reply by OverFlow

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

The lack of development of BartPE and this project for that matter is simple. People who invest a boatload of their time go unappreciated both monetarily and in practice. It is a sad truth that people who want something for nothing do not appreciate getting it. The best way that I can describe it is that they present a false sense of entitlement. This is not motivational for people who invest thousands of hours of personal time. No respect and no money. life is short. Other things to do. Real life is awesome. Hilander999 (the guy who wrote MOST of all the code for UBCD4win is a very good friend of mine. He doesn't even read the forums anymore. Moreover since PE3, 4, 5 are out PE2 is not going to change.

The short answer is there is no PnP in BartPE. I said this in my previous post.
Think DOS, you want to know why you can't load windows drivers in DOS.
I know it LOOKS like windows. It's not, it's PE, it is nothing like windows.
To load chipset requires another plugin called HWPnP by paraglider, HWPnP never progressed to the level that would allow full blown drivers in PE.  UBCD4Win Includes the best version of HWPnP available, but it is still not a replacement for windows PnP. I know what your thinking, load chipset and it will make my service of the machine faster! doesn't work like that. you are still running the 16 bit DOS driver, (mass storage text mode driver). HWPnP's main purpose is to enable basic drivers like WLAN and video.

It is possible to force BASE to do what you want but it will very likely be unstable. I recommend against it.
It is fully supported by DriverPacks BASE, but it is not supported by BartPE and therefore grayed out (disabled).
DriverPacks BASE is, and has been, fully capable of creating plugins for any DriverPacks that DriverPacks BASE supports. They will seem to be disabled until HWPnP or equivalent plugin is created to support them. Many of the packs themselves have already been optimized to create plugins for testing as well. So from a DriverPacks perspective creating the plugins is a snap. Having a stable PE platform is a different story.


Hope that helps

PS I took the time to reply because it is obvious you are not one of the people I described.

Go to forum: Feedback and Support - DriverPacks Base

96 Reply by OverFlow

(5 replies, posted in Windows 7 Discussion)

several of our offerings do this, SAD, Snappy driver and dp solution. they all do this.

HWIDs tool in my signature does this, without the compare to database of course.

Go to forum: Windows 7 Discussion

97 Reply by OverFlow

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

you are not missing anything.

the only packs needed are mass and LAN, occasionally certain Intel video cards (that don't support VESA). WLAN is select-able but can be problematic. Certain options are grayed out because they don't work.

Mass storage is not selected because it is not slip-streaming to windows, this is correct.
Mass storage textmode is selected because that is what is used at the PE stage of windows, this is correct.

Chipset is not needed. remember this is PE NOT Windows. Sound won't work either tongue.

Think to self; i am running a 16 bit version of a 32 bit OS so only the most basic stuff is going to work. That is not entirely true but it will put you in the correct mindset without a bunch of complicated explanations. This may also help, no PnP in PE wink.

It's a repair tool, not an OS replacement. It is solid and it works.
It will never work the same as windows, close sure, but not the same.

Go to forum: Feedback and Support - DriverPacks Base

98 Reply by OverFlow

(8 replies, posted in Windows 7 Discussion)

I got your email however i can not help you with DriverPack Solution issues

Go to forum: Windows 7 Discussion

99 Reply by OverFlow

(8 replies, posted in Windows 7 Discussion)

sure, shoot me an email via forum

Go to forum: Windows 7 Discussion

100 Reply by OverFlow

(4 replies, posted in Windows 7 Discussion)

this might be able to be done, but is beyond the scope of this forum.

we try extremely hard to NOT modify drivers,
we simply take (unmodified) original drivers and bundle them conveniently.

having said that take a look at the inf file of your driver... does it have a section for win7? no... maybe you could add one? look at other drivers for examples of how. MSFN.ORG may have info and users to help. that is where this site got it's start wink.

best of luck, report back and let us know how you did big_smile.

Jeff


A Word to the Wise:

I know of at least one individual who was sued for doing this, the manufacturer released a crippled driver for VISTA. One user modified their Vista driver to enable all the same features that are / were available in XP. (and released it publicly) They slapped a cease and desist order on him and threatened to levy monetary damages. (this was / is a well known audio card manufacturer)

Go to forum: Windows 7 Discussion