651 Reply by OverFlow

(2 replies, posted in DriverPack Graphics)

just supply the requested info...

"Read BEFORE you post" AKA Rule #0. you had to agree you read this to join.
It is also linked in my signature.
(The pointed questions have already been provided to you in advance)
If your memory is as bad as mine you can click the "rules" link on the top menu and look at what you agreed to again. here is the first four lines.

Less is more: no extensive rules. Simply act responsible.
Here are some helpful tips to help you with 'acting responsible'.

0. Read this BEFORE you post.

Be absolutely sure you read that BEFORE you post.

You got most of them by accident... but you missed the most important sections of rule #0: #4 and #5 : 
IE - Pack and BASE versons used, DPs_BASE.log - DPsFnshr.log related parts of setupapi.log, HWIDS.

All the stuff that we ABSOLUTELY MUST HAVE to help you... and that we requested (begged) you to provide in your first post.

We don't need a novel... just the stuff we list in "Read BEFORE you post" (maybe we need a better name for it, hmmmm) wink  tongue

Welcome to DriverPacks, looking forward to assisting you.

PS you nailed #6 Good job on that big_smile

PSS Driverpacks are not designed to be used with winnt32.exe based setup... how did you address that issue?

Go to forum: DriverPack Graphics

652 Reply by OverFlow

(7 replies, posted in Site & Forum Issues And Feedback)

there is ... but it is not a feature of this BB software.

Go to forum: Site & Forum Issues And Feedback

653 Reply by OverFlow

(60 replies, posted in 3rd Party DriverPacks)

no limit on files in a pack... # of folders can become an issue as it adds to path length.

Go to forum: 3rd Party DriverPacks

654 Reply by OverFlow

(60 replies, posted in 3rd Party DriverPacks)

I don't know.

Go to forum: 3rd Party DriverPacks

655 Reply by OverFlow

(5 replies, posted in Site & Forum Issues And Feedback)

Woo hoo! Hope to see your server added to the list soon.
once you get online Wim will prolly add you to the donors group and you will enjoy access to our testing team forum too. That will enable youto get a sneak peak at our latest work in progress. Perhaps you can even help with testing...

Again - Thanks for your interest (and generous offer) and welcome to DriverPacks.net

Jeff

Go to forum: Site & Forum Issues And Feedback

656 Reply by OverFlow

(78 replies, posted in Vista / 7 DriverPack Audio)

mirecek1965 wrote:
Fragbert wrote:

FYI: Creative folder "6" fails to integrate via DISM (has SBXF and XFHX folders) for Windows 7 x64, all others integrate fine (code '0')

I confirm this, on late driver packs cannot integrate Creative X-fi :-(

I seem to remember that the creative drivers are one of those that rely on the finisher to install correctly. I haven't updated the finisher to run on Windows NT6 yet. I really need to do that. My free time has been at an all time low this last year. Being self employed and in the USA i have been scrambling to make ends meet, and I am loosing ground sad.

You will probably find that the setup must be run on boxes that have creative hardware in order to install the driver properly.

Jeff

Go to forum: Vista / 7 DriverPack Audio

657 Reply by OverFlow

(5 replies, posted in Site & Forum Issues And Feedback)

I believe that is intentional, only Wim knows for sure.  He may chime in here...

We get very little in the way of donations / revenue, one way we are able to get donations are thru our banner ads on the download pages. Linmin for example is one of our biggest contributers. in order for us to realize that revenue stream we need to demonstrate page views. The more page views the more value those banner spots represent. It is very important to us (and to you) to be able to keep the lights on here at DriverPacks.net. Since we almost never get donations that is the only way we can pay the server bills.

Thanks for your interest and welcome to DriverPacks.net

I'll bring your request to Wim's attention.

Jeff

Go to forum: Site & Forum Issues And Feedback

658 Reply by OverFlow

(13 replies, posted in DriverPack Mass Storage)

PaulDG wrote:

Maybe the base processing code evaluates the tag name as a variable or in a key/value pair, In which case its overwritten by the next duplicate entry.

Many Thanks

Yeah there are several multi-dimensional arrays that are used and copied / collated / sorted and some are local functions and some are global. it is quite involved to go back and forth from module to module to subroutine... etc. but the bottom line is the same... no duplicate tags or the GIGO error occurs. and reading a BASE log in debug mode is a long read too big_smile.

Go to forum: DriverPack Mass Storage

659 Reply by OverFlow

(13 replies, posted in DriverPack Mass Storage)

just as a side note...

if you are doing RIS based setup perhaps consider AutoImage by RogueSpear.. it is no longer updated or supported by him but is quite solid and works beautifully with DriverPacks... the forum is still on line and the downloads are still available. Also it is something we are familiar with big_smile.

Go to forum: DriverPack Mass Storage

660 Reply by OverFlow

(60 replies, posted in 3rd Party DriverPacks)

be cautious... removing certain files, and we don't always know which ones, will break signing.

Be sure to test signing after you delete files. if i remember correctly this can be done with "sigverif"

It's always better to maintain signing if possable.

Go to forum: 3rd Party DriverPacks

661 Reply by OverFlow

(13 replies, posted in DriverPack Mass Storage)

I can think of a good reason to not reuse a tag name even if it is only used once per OS...  It should only affect QSC = enabled. But apparently that is not the case.

If QSC is on all files are output to the QSC folder (XP, 2K3 and 2K) regardless of which OS is the current target. Programatically this needs to be done because we don't know which OS will be the target the next time BASE is run smile. So if the tag name is reused only the last file copied to the cache will exist. In this particular case of ITE it would in theory be no issue because the source file is the same for all three. however if the source were not the same only the last file copied would be the correct one. (the xp file overwrites the 2k3 file or whatever)

Go to forum: DriverPack Mass Storage

662 Reply by OverFlow

(13 replies, posted in DriverPack Mass Storage)

PaulDG wrote:

Something to do with QSC? - As all drivers are pre compressed.

PG

nope because i never use QSC when i am testing ... it might skew my results big_smile
I tend to use the same file name over and over again...
if the file name don't change the cache is used instead of the new file. So any changes would not show up in my results.

Plus QSC is only useful if one intends to slipstream the same mass storage pack multiple times. I never do wink.
Additionaly using or not using QSC will not alter the final result (unless the driverpack is altered after using QSC)... the files are simply output to a temp folder and then copied to the destination. the same exact code is used in both instances the only difference is the output folder. (and a copy if QSC is on)

@Paul That's a valid guess for someone who doesn't have the code in front of them big_smile.

Also the source file is the same for all three... so the cache is valid in any case. The issue is with how the mass INI is processed by BASE. The mass storage code is over a thousand lines in several modules in at least three different files... (it's pretty complicated) somewhere in that mess is the answer... i could not find it quickly... but the fix is simple and the same as it has been for the last 7 years... don't duplicate the tag name big_smile.

Hmmm... this makes me think...
Note to self and smartepants:
If the files won't be changed and only the mass INI needs to be altered one may speed up testing by simply altering the contents of the mass INI in the QSC folder big_smile big_smile big_smile!

Thanks Paul your question has taught me something smile

Go to forum: DriverPack Mass Storage

663 Reply by OverFlow

(13 replies, posted in DriverPack Mass Storage)

[IT1]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA XP"
ms_1_tag="iteatap1"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k3,w2k"

[IT1-2k]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA Win2000"
ms_1_tag="iteatap0"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k3,wxp"

[IT1-2k3]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA Win2003"
ms_1_tag="iteatap2"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="wxp,w2k"

yep... can't have a duplicate name even if it is technically skipped ...

the above code works (GIGO Erik)

[IT1]
ms_count=3
ms_1_deviceName="ITE IT8211 ATA XP"
ms_1_tag="iteatap0"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k3,w2k"
ms_2_deviceName="ITE IT8211 ATA Win2000"
ms_2_tag="iteatap1"
ms_2_sysFile="iteatapi.sys"
ms_2_hwids="PCI\VEN_1283&DEV_8211"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k3,wxp"
ms_3_deviceName="ITE IT8211 ATA Win2003"
ms_3_tag="iteatap2"
ms_3_sysFile="iteatapi.sys"
ms_3_hwids="PCI\VEN_1283&DEV_8211"
ms_3_isBusExtender=false
ms_3_exc_skipIfOS="wxp,w2k"

also fails sad

why is this anyway... why not 

[IT1]
ms_count=1
ms_1_deviceName="ITE IT8211 ATA"
ms_1_tag="iteatapi"
ms_1_sysFile="iteatapi.sys"
ms_1_hwids="PCI\VEN_1283&DEV_8211"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS=""

somebody broke the oldest rule in the book "no duplicate tag names"
Although as i looked through the code i fail to see why it wouldn't work hmm

Go to forum: DriverPack Mass Storage

664 Reply by OverFlow

(13 replies, posted in DriverPack Mass Storage)

now that is strange... Looks like i will have to break out the code...
I can't remember off the top of my head why that would not work.

although the rule has always been no tag name may be duplicated.

that may also apply to sections that are technically excluded...

BRB

Go to forum: DriverPack Mass Storage

665 Reply by OverFlow

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

post your DPsFnshr.log and your DPs_BASE.log

Welcome to DriverPacks.net

Go to forum: Feedback and Support - DriverPacks Base

666 Reply by OverFlow

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

use the fully working dvd... (simplest easiest first)

anything else (like sysprep) will take a HUGE amount of your time and not work as well.

You should try RIS using autoimage... I am sure you will have your best shot at a working server / client setup going that way. AutoImage will cure your issues with Unnattended settings, presetup.cmd, ect... when switching to a winnt32 based setup.

Welcome to DriverPacks.net

Go to forum: Feedback and Support - DriverPacks Base

667 Reply by OverFlow

(4 replies, posted in Hardware)

That is a REALLY OLD card... over ten years old.... If there is a driver then 3Com (HP) should have it...  I am surprised it is not supported by windows 7 natively...

3Com is now owned by HP... the drivers have not been updated since 2001... and probably never will be again, since it is almost a 15 year old product line. (in computer terms two years old is considered obsolete)

http://answers.microsoft.com/en-us/wind … 128c19935a

leads to...

http://www.microsoft.com/windows/compat … ;os=64-bit

Use it in an XP machine and call it a day big_smile... Get a new card for win 7 hmm
You got 10 good years out of it... not enough? tongue

Moved from "Feature Requests" to hardware

Go to forum: Hardware

668 Reply by OverFlow

(23 replies, posted in Universal Imaging)

Yes you can backup and restore a user profile... as long as the user profile is not married to a specific machine in the domain. (roaming is allowed).

Go to forum: Universal Imaging

669 Reply by OverFlow

(2 replies, posted in Other)

Welcome back team dude... Always nice to see you here!

Go to forum: Other

670 Reply by OverFlow

(10 replies, posted in DriverPack Mass Storage)

It's a standard IDE drive... I cant think of any reason it would not be available... It should not even need a driver.

It looks like the controller is installed correctly...
does it show up at all in Device manager?

Go to forum: DriverPack Mass Storage

671 Reply by OverFlow

(6 replies, posted in Installation Platforms)

post your DPs_BASE.log... that should tell the story
perhaps the contents of your winnt.sif too (the final one, remove any sensitive data like PID key password ect... tongue)

Go to forum: Installation Platforms

672 Reply by OverFlow

(23 replies, posted in Universal Imaging)

We don't change the NTLDR file... So there is no need to replace the file with an original... it is the original.

In fact we don't change any OEM files

Go to forum: Universal Imaging

673 Reply by OverFlow

(5 replies, posted in Universal Imaging)

if there is only one dhcp server on the network then an IP should not be duplicated... unless there are attached devices with static IP's (a client issue, if reservations are not set for the static IP's on the DHCP server), that seems like a dhcp server issue.

Go to forum: Universal Imaging

674 Reply by OverFlow

(3 replies, posted in Universal Imaging)

please read (skim, search) through the stickied topics in this (universal imaging) forum.

this looks similar based on your HWID (I used search big_smile)
http://forum.driverpacks.net/viewtopic.php?id=2835

Go to forum: Universal Imaging

675 Reply by OverFlow

(10 replies, posted in DriverPack Mass Storage)

never do KTD all...

I am sure you have no use for LAN-RIS (Remote Installation Services) since you  are installing from a disc.

that method should work... Did the driver install? if not you could include the relevant section of the setupapi.log file.

Go to forum: DriverPack Mass Storage