Yes the inf requirements are optional...
Would you care to post your Pack to the 3rd party DriverPack forum here at DriverPacks when you think it is ready?
I bet lots of people will appreciate it!!!
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
Yes the inf requirements are optional...
Would you care to post your Pack to the 3rd party DriverPack forum here at DriverPacks when you think it is ready?
I bet lots of people will appreciate it!!!
totally understand...
Those files contain info that allows the team to share info about what was done and hopefully by whom without having to read through the whole thread where it is posted . It also makes it easy for one team member to pickup where another had left off...
It also will allow those 'sneakers' to see what the changes were / are
Especially since they don't have access to the testing team forum to view the comments that are posted there ...
that is to say that they are helpful to people like you LOL
Alternate solution: Unpack the nightly read the notes and repack without them. It is a win win solution!
PS
Giving feedback on success or failure of a nightly is considered VERY COOL, and just may earn you testing team status . BigBrit is my testing team hero - he will almost daily post a HWIDS dump (In code tags! ... Thud.) followed by "It worked perfect!" and that is just about as good as it gets for the packs team and myself!!! It's like winning a game, match or race. Praise and donations are rare at a support forum. The only thing more elusive is help
.
It usually impresses me that they were found and used, since it demonstrates resourcefulness. I will often respond with a comment like "He used Search! Thud... Sorry I fell out of my chair!" The nightly server is not a secret, but it is not openly advertised either... I reason to myself if they can find it / them on their own then they are probably bright enough to deal with any issues that may result from using them.
Which brings me to another point, we only have a handful of people who work on them, and its not easy to update them. So it takes a while to get them stable enough to release. We prefer to have stable and reliable DriverPacks rather than having up to date ones that cause BSODs or other poor results. We would rather get a report of a missing driver or have a report of an out of date driver than get a report of a crash or corruption.
try one line with "atidemg?.dll"
LOL you were doing so well now i have to thwart you...
Since Nightlies are for testing only no command to remove the text files will be added to the process...
You were going to format it and use the official releases for actual production machines wern't you?
Everyone knows Nightlies are never to be used for production. and official releases don't have .txt files in them
ROFL have a happy new year!
Thanks for the feed back!
PS that is one of the tip offs that a user is sneaking into the nightly stash
They say something like i get these strange XML and TXT files in systemdrive... WTF?
It's a dead giveaway they are breaking the rules. LOL!
you tell me... I don't have one of those to test for you
Um...
have to agree with you that there probably are not any commercial ones...
But lets face it if you own a company and have employees,
have an office with multiple PCs,
then you can and should Buy a top ten AV program. Yes?
for private individuals there are a few for FREE and WITH resident protection like avast
http://www.avast.com/eng/avast_4_home.html
http://anti-virus-software-review.topte … eview.html
here are some independent av reviews (some free with real time - for personal use)
http://www.pcmag.com/search_redirect/?q … amp;site=3
http://www.cnet.com/topic-reviews/antivirus.html
http://www.top10list.com/top,10,antivir … ection.asp
http://www.firewallguide.com/anti-virus.htm
one I got a big kick out of was this one the 69 worst antivirus scanners LOL
As always, I recommend that everyone should remember to STFW!
Jeff
PS
This post is my personal opinion and is not intended to be an endorsment.
DriverPacks does not endorse or promote any software except DriverPacks BASE.
(except perhaps apps provided by RogueSpear, Nuhi, RyanVM, Siginet, Bart Lagerweij, KickArse and WarmSnow - and the UBCD4Win team)
The opinion here is not neccessaraly that of DriverPacks.net, the DriverPacks team or Bâshrat the Sneaky. (but it might be)
the links above are provided for informational purposes only.
Any info on linked pages is the opinion of that site.
furthermore
The author of this post makes no representations or warranties about the information provided through this post, including any hypertext links or any other items used either directly or indirectly from the post and reserves the right to make changes and corrections at any time, without notice. The author accepts no liability for any inaccuracies or omissions in this post and any decisions based on information contained in this post are the sole responsibility of the guest. The author accepts no liability for any direct, special, indirect, or consequential damages or injuries or any other damages or injuries of whatsoever kind resulting from whatever cause through the use of any information obtained directly or indirectly from this post. Warning bashing your head against the wall can be painful and cause brain damage. Please make sure your workstation is ergonomicaly correct before proceeding.
We would however like to express our eternal gratitude and sincere thanks our Sponsors
LinMin and Simple CDN
PSS Hows that ?
Happy New Year!
Sorry to all of you to whom my best wishes arrived a little late
Moved to the News forum!
PS Hectorfx, your name is now on the home page!!!
Strange that none of the compatable ids were PCI\VEN_ format...
What about in the Hardware Ids selection?
For my HP NC3163 Fast Ethernet NIC I get
Hardware Ids
PCI\VEN_8086&DEV_1229&SUBSYS_B1340E11&REV_08
PCI\VEN_8086&DEV_1229&SUBSYS_B1340E11
PCI\VEN_8086&DEV_1229&CC_020000
PCI\VEN_8086&DEV_1229&CC_0200
and
Compatable Ids
PCI\VEN_8086&DEV_1229&REV_08
PCI\VEN_8086&DEV_1229
PCI\VEN_8086&CC_020000
PCI\VEN_8086&CC_0200
PCI\VEN_8086
PCI\CC_020000
PCI\CC_0200
but that is on Win2k3 (not r2)
I have
wnt5\BXVBD.INF=20,,1
wnt5\BXVBDX.SYS=4,,1
Excellent...
Sorry for my inexperience:
Did you mean the \D\L\B3\BXVBD.INF file contained in this .7z pack?
Yes
- what is the portion of the HWID string I have to search for in this bxvbd.inf file?
In the DP_LAN_wnt5_x86-32_90904.7z pack version of this file I can find only the generic string
All you need is the generic string...
In device manager go to device properties and select the details tab...
Select "Compatible Ids" from the drop down...
You do see the generic ID pci\ven_14e4&dev_164c included in the compatable list?
That means the driver does match / is compatable with the device
while in the downloadable HP version of that file I can find both
%NC373i_desc% = NC373i_inst_x86, pci\ven_14e4&dev_164c&subsys_7038103c
and
%NC373T_desc% = NC373T_inst_x86, pci\ven_14e4&dev_164c&subsys_7037103c
That driver is also a match... if you were in windows (which we are not) it would be prefered to the generic match.
I think i need to get one of my buddies from the UBCD4Win team in on this.
I belive we need some registry entries added to your build to make this fly
Thanks for the feedback... It makes the plugin(s) better for everyone!!!
PS i was not aware that 2k3 R2 was supported... have you tried a build with just regular 2k3 (or XP)?
That HWID is not supported in our latest Nightly either...
Will get that put in...
Thanks for providing such good details!
Have a great day and Welcome to DriverPacks!
tutorial in my signature...
Read BEFORE you post in my signature...
browse our Rules and Posting Guidelines
vmware / virtual box may be a way to get there
in UBCD4Win350\plugin\DriverPacks.net\LAN\lan.inf
can you find these lines?
nt5\BXVBD.INF=20,,1
wnt5\BXVBDX.SYS=4,,1
that HWID is actually for a Broadcom NIC... HP had to get it from somewhere
And is included in the pack you are using, in folder
DriverPacks\DP_LAN_wnt5_x86-32_90904\D\L\B3\BXVBD.INF
can you verify the md5 sum for that pack is E28C281D8933772E8E3BB9B3C62BF9C5 ?
I suspect that there could also be some missing registry entries that may be required to allow it to work properly.
let me call in a favor...
did you try this http://www.mydigitallife.info/2008/06/3 … and-linux/
Nice! Now that is how its done!
Woo Hoo!!!
Hey all you DriverPacks noobs out there - Look at the posts above. It's a perfect ten!!!
I will let Major take a crack at it first since he has been working the sound packs...
I'll jump in if needed!
Happy New year RedWine!
Jeff
PS since you seem to be using all the test packs anyway and obviously can provide excellent feedback. I have added you to the testing team so at least you can see what is going on with them. (there is a previously hidden forum that is now visible to you.) If you are going to use them you should be in the loop. Please remember test packs or nightlies as we call them are for testing purposes only - not for production - if they were fit for use by the public then we would have released them
Welcome to the testing team... Grab you a user bar!
full list is here! http://e1h7.simplecdn.net/driverpacksnew/other/userbars
PSS did you try installing with the official releases of sound?
Major is still learning the ropes, and the sound packs are a real bear to get right... even for our most veteran pack team members.
@All - Please try to stick to the official releases, or at least our RC versions, for production machines!
one in a millon gives even a dollar... I try to recognise when you are that one in a millon!
Wim is a college student - i remember what it was like when i was in college!
I am not aware of any specific issue...
if you tried the original drivers from them and they failed too then it may be a hardware conflict that only exists on that specific machine or the drivers you found and the ones in the pack have the same issue
Thanks for reporting and agian i am sorry it toook me solong to respond to your issue!
Happy New Year!
PS KTD all is not a good idea... chipset mass and graphics are unlikely to ever change .
My personal server is a ML530 G2...
They are a very nice series of servers
added code tags to your post
Always Happy to help one of our generous donors!
Sorry I did not respond right away...
please post your DPs_BASE.log,
the HWIDs tool in my signature helps to post your HWIDs. (I do see them included above )
Code tags are always appreciated too...
They keep the posts / threads from getting too long
I added them to your post above to demonstrate.
They were not absolutely neccessary but they will be for your DPs_BASE.log
Hint: If you edit your post you can see how that is done
Hint: DriverPacks BASE archives old logs in \DP_Base-Install-Folder\LogFiles\
You're looking for one of the larger ones, and they should be dated;)
Happy New year!
Again I am sorry that I missed your post before!
Jeff
here is the main idea... A MAC address is supposed to be Hard Coded into the ROM on the device itself...
That is why MAC address were once good for security purposes...
Because they were intended to Not be able to be set from software.
At least that was the original intent, The Theory was no two devices would ever have the same MAC address.
and routers could use this ID for preventing access to networks...
If the MAC address was Hard Coded into the NICs ROM (Unlike an IP address that is alterable from software)
as proposed in the original THEORY the only way to change a MAC address was to get a new NIC...
In the old days Flashing the ROM on a NIC might set a new MAC address...
But in THEORY it still should not have changed
It was intended to be BURNED INTO the HARDWARE Permanently ...
What a great security measure! You could as a network admin POSITIVELY ID a specific PC / NIC (like a drivers license)
http://en.wikipedia.org/wiki/MAC_address
"Although intended to be a permanent and globally unique identification, it is possible to change the MAC address on most of today's hardware, an action often referred to as MAC spoofing"
Over the years this really excellent plan was shot full of holes...
First they allowed changing it during a BIOS / ROM flash. Later by Driver and eventually by Registry.
Now making it totaly useless to anyone at all...
So why do you wish to change this totaly useless number?
Please read the post directly below yours... TIA
[SLVD] Toshiba MK2555gsx ATA Drivers
PS please note that other than providing your HWIDs, (Kudos to you for that!!!
)
you have duplicated all the same omission of key detail mistakes.
Put another way, you have shown the same blatant disregard of "Read BEFORE you post", (rules and guidelines rule #0)
PLUS not searching.
I think your fix is the same fix as his,
but I can't be absolutely sure because you have provided insufficient details.
I hope and sincerely believe you will find the same fix applies to your request,
if not (or even if so) please provide the rest of the required info .
[OS; type, version, language, SP level.
DriverPacks; DriverPacks BASE version, DriverPacks used and their versions.
(Hint: all of the above listed info is included in your DPs_BASE.log)]
Looking forward to assisting you.
Have a great day!
TIA again!
PS Good job smiley for using code tags too!
at this rate i may have it fixed in DriverPacks BASE before i explain how to do a workaround .
I just double checked presetup.cmd .... And I was mistaken!
devpath is run from the CD/DVD it is NOT copied to systemroot like I thought... (embarassed) Sorry!
perhaps you are attacking the problem from the wrong angle...
many NICs allow you to SET the mac address
sometimes this may actually require flashing the rom.
Spoofing is a hacker activity sir - are you being a bad boy ? ? ?
PS mac OS 10 IS linux... so if you can do it from linux then you can also do it from OS X...
were all of the other files there? the \D\ folder and the ini files, the finisher, mute, ect?
the problem with runonceex and guirunonce is they don't stop...
the commands are executed one right after the other. Bam, bam, Bam.
there is no waiting for the first command to finish before calling the second or third or forth one.
That was why I was quick to point out that I had not tested it .
It may work as intended if you create and call a script
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 1 /D "%SystemDrive%\MyKTD.cmd"
myKTD.cmd
start /wait copy %SystemDrive%\D\3\pack1 %SystemRoot%\D\
start /wait copy %SystemDrive%\D\3\pack2 %SystemRoot%\D\
start /wait copy %SystemDrive%\Devpath.exe %SystemRoot%\D\
start /wait %SystemDrive%\DPsFnshr.exe
%SystemRoot%\D\Devpath.exe %SystemRoot%\D
in this way you can insure that the commands are executed one after the other, instead of all being called at the same time .
you could add a few lines or call a script from the presetup.cmd file as an alternate solution
as i said i can think of 100 different ways to pull this off .
That is a perfect post! Well done.
We'll take a look at it... were you able to add it yourself? If so then what driver did you use?
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.222 seconds, 5 queries executed ]