You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 19 of 213)
Topics by OverFlow User defined search
Posts found [ 451 to 475 of 5,307 ]
hooking up an external drive wont do anything to his TV it will either work or it won't...
you do have another option... use partition magic to create a fat32 partition... you can easily create 128 gig partitions. You can actually make them even larger but for reasons i don't wish to include in the scope of this discussion i would not recommend it.
the actual limit of fat32 partitions is much larger than windows will allow you to create. (in theory its 2 TB)
third party applications will create them and windows will use them without complaint, you can even run chkdsk on them.
it's prolly Linux based... try formatting a drive with a Linux distro and see how you fair that way 
.
because we like to banter while we wait for you to come back 
and techdud was not entirely wrong, it is often an overlooked problem.
I could have made the same argument for video cards... if a video card has an issue it can make anything happen, including cause your floppy to fail. A bad video card can make it "anything can happen day". I have fixed some VERY obscure issues by swapping out the video card... believe it or don't.
I think what we all agree on at this point is you do have a Hardware problem, the only mystery is which component...
PS no you did not have 3 bad floppy drives... odds of that happening are pretty slim
Wow Ra you are a busy boy!
Thanks a million!
regarding power supply and wattage an often overlooked stat is the duty rating...
i like the antec true power units for that reason. many power supplies have a duty rating of 80% some as low as 60%
what this means is a 1000 watt power supply with a 60% duty rating can only put out 1000 watts for a second or even a fraction of a second. it is only capable of supplying continuous power of 60% of 1000 watts continuously or 600 watts
so many decent 1000 watt power supplies are really only 600 to 800 watts.
UNLESS you get a unit with a 100% duty cycle rating (Like an Antec True Power). These are usually a lot more $$$.
In conclusion a 600 watt PS with a 100% Duty cycle is a better power supply than a 1000 watt unit with a 60% Duty cycle 
.
It is also truth in advertising... implies a reputable manufacturer.
play with that last one and see if you can get it yourslef... LOL
you're having some issues with nested quotes... fixed for ya
did you see my last post
Welcome to the testing team...
You will find that several new forums are now visible to you.
Thanks for being here and all that you bring to our forum.
Jeff
Caleb37 wrote:This part is not true. When you add TEXTMODE single driver through nLite, either before or after DriverPacks, and trust me I've tried both ways, the two sources conflict with each other because they both write to many of the same files. Not only that nLite adds iaStor.Sy_ and this folder NLDRV with the RST package in a subdirectory in the I386 folder. They are referenced, I believe, in the txtsetup and dosnet, and a few other files, which DriverPacks seems to do as well. So they appear to be receiving direction from two different sources and I think this is what causes the conflict. When I tried using TEXTMODE Single Driver through nLite and then adding DriverPacks, I did not include MassStorage pack because I was certain this wouldn't work. But that being said, just including the Chipset, LAN, WLAN, and SoundB at the end WOULD not work. It creates a BSOD even before Windows setup load files. The two broke each other.
TRUST ME... I know exactly how this all works. I am not wrong.
PLEASE re-read what i posted above
that would work IF there was not a HWID conflict in the pack, which there is.
Please be aware that is how DriverPacks got its start.
Wim Leers our founder (AKA Bâshrat the Sneaky) was laughed off of the MSFN forum for suggesting that the DriverPacks project was possable.
Please take a moment and find Bâshrat the Sneaky on MSFN and see for yourself. Obviously it was not and is not impossible.
Anything that can be done in nLite can be done without it... and in a better manner.
NOTE: I do use nLite myself . however i use it for very few and very specific things...
IE The create ISO function is very useful.
Never let anyone make you belive something is impossable, do as you have done let it motivate you .
If you have access to hardware and don't mind reloading a machine when you have time I'll add you to the testing team...
NOTE: i keep a second partition on my HDD just for testing new builds of my unattended installs
Jeff
I would like to apologize to everyone that i got here so late in the game!
You guys did an awesome job on this issue though!
Thanks for jumping in and running with the ball!
Jeff Herre
DriverPacks admin
@TechDud
Will you make sure that this duplicate is fixed in the mass storage pack next time you are in there?
NO Duplicates allowed, so if you see any others stomp them out!
Please start to use code tags as well ... see your previous post with your HWIDs to see how i "fixed' your post .
Caleb37 wrote: MSFN told me I couldn't remove DPBase packs from an nLite source after the fact, yet I wrote a batch file that did exactly that, including replacing the original nLite files in the I386 folder.
Not exactly true, DriverPacks can be removed IF DriverPacks was the LAST step in your process.
you could add your textmode driver in nLite then add DriverPacks... and that would work IF there was not a HWID conflict in the pack, which there is. HINT: remove the section(s) {there is normally only one } of the Mass Storage INI with conflicting HWIDs HINT 2: set MScount to 0 (zero) will disable a section...
nLite first then DriverPacks. If you do DriverPacks last then you can always remove DriverPacks. (to remove DriverPacks simply run DriverPacks BASE on your source with no packs selected .
We never recommend using nLite, it really wacks the source, however if your not comfortable or experienced with OS installation it can be helpful. Just be aware it is a really messy thing to do to your source. But if it works for you on this one machine then go for it.
Damnation wrote:OEM LINK
http://downloadcenter.intel.com/Detail_ … ldID=20963
If he ever comes back, I've noticed that this hardware ID
only uses megasr.sys in the OEM driver, same in driverpacks. but driverpacks has the addition of iaStorA.sys also with that HWID.
If mass-storage.ini is edited to remove this HWID from iaStorA.sys I think it'll work.
Duplicate HWIDs are not permitted... this is an error in the pack.
Caleb37 wrote:Well, look I thank you for your help. I've wasted enough of your time. I was under the impression using this forum I could learn how to modify a driverpack to suite my needs, but it's a challenge that can't seem to be done. So again, thank you. I'll continue to try to figure this out on my own, at this point, or collaborate with others that have been successful at doing this. I don't mind using the TEXTMODE single driver, but then I lose the ability to include the Driverpacks I've been using for years in combination with nLite and now that seems to be lost because of this idiotic situation with Intel, the X79 Chipset, and Windows XP32bit.
Sorry to have troubled you with a challenge that can't be met.
That is not at all true. We have a very thorough guide for doing this exactly.
It is naturally in the FAQ (Frequently Asked Question) section of our forum.
IDK why you were not immediately pointed to this thread...
http://forum.driverpacks.net/viewtopic.php?id=2461
tattooed_pariah wrote:I might see if the IT guys at work have a USB floppy I can borrow.. I'd hate to waste money on something I'll use once.. I already blew $10 on a standard floppy drive today..
I doubt you had two bad new floppy's in a row, you were probably right in suspecting the ribbon cable.
Please use the connector at the END of the ribbon cable if there are two connectors, (last con. is "A" drive).
Please borrow a Floppy drive ribbon cable from the IT guys at work~
the F6 driver (floppy driver for txtmode) is on this page
http://www.asrock.com/mb/NVIDIA/ALiveNF … &os=XP
listed as SATA RAID Driver (For system to read from floppy diskette during Windows installation)
Techdud is right about the PSU being an often over looked issue. I keep a known good test PSU on my bench.
HOWEVER floppy drives are not sensitive at all to poor power input . If there is any power at all it should blink and buzz .
The ribbon cable or the MB is the issue. (make sure you did not bend a pin over on the MB connector .)
best of luck sir.
Thanks for confirming the issue is resolved .
Jeff
Damian666 wrote:thanx man :-)
i coded it in autoit, and you're welcome to use anything to make sad better.
on that note, i always wondered why sad was'nt recoded with a Gui...
and yes, i know the torrent client is big, i cant seem to compress it, nor did i find a better or smaller one, most are linux builds.
the dht file is'nt updated by the program, but could be if i had a direct link.
Damian
edit, whoohoo, got a sticky xd
The GUI version is my fault... When i get some time i will punch it out. It also needs to have the DriverPacks Finisher updated and added.
nLite integration corrupts the source.
Creating the ISO with nLite is FINE .
I sent Wim a message to weigh in here.
But yes i think if you made that modification then it would be permisable.
your work is awesome. I also did a similar thing in DriverPacks BASE, except i relyed on an external P2P client.
Simply modify your app so they must view the download pages of the packs they wish to download and then it will be perfect .
I am not saying you can't do a downloader just that you need to avoid robbing us of our page hits in the process .
Thanks for understanding
Jeff
I will repeat ... i had update function built into DriverPacks BASE.
Wim Leers. AKA Bâshrat the Sneaky founder of this site and our leader. made me disable it.
He wants people to go to the download pages themselves and physicaly SEE the pages.
Otherwise I would still have this feature built into DriverPacks BASE.
Your project (as it is) goes against the wishes of the founder of DriverPacks.net.
to be inline with his wishes your app should direct the users to the download pages of the files.
IE open a browser window to the download page so they can select the download.
If you like i can ask him to explain it himself in case i have not worded it properly.
Agreed DriverPacks BASE reports Beta, Alpha, Release Candidates and Third Party as "Where did you get that?!" Humorus and to the point .
I would also like to remind the reason Wim made me pull the updater in DriverPacks BASE is because we need page hits to attract advertizers on our site. that is how we pay the server bills. To keep in line with his wishes the user must be directed to the page to click the download links (viewing the page).
Posts found [ 451 to 475 of 5,307 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.131 seconds, 9 queries executed ]