You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
Thank you so much...
that is an excellent observation and a situation i had not considered.
i will make the suggested changes to make it resilient against this.
thanks for not only finding the problem but providing a possable solution as well.
I am going to tag your post as a [REQ] for you.
if you like you can create a "bug" report so i wont forget, and it is a rare opportunity 
the bug tracker here plays cards with the maytag repairman...
this is the path to the dark side Luke...
this method leads to sysprep... which is not directly supported at the moment...
Check out Universal Imaging topic for some tips from other users who are doing what you are attempting.
however you may have some additional luck by changing the HDD controler type to standard IDE before shutting down and imageing. that may at least get you past the dreaded 7B BSOD.
the DriverPacks were intended to be used during installation. there may be support for ris or sysprep in the future.
if you check out the FAQ page there is a sticky about drivers only CD and post install DriverPacks installation
it is amazing how people jsut dont stop to think about
how much time is involved in doing what they percive to be easy
of course they cant or wont, but they will diminish it anyway...
second the offer to show us the money...
Well RIS and sysprep are on Bâshrat the Sneaky's long term goal list so adding features that take us in that direction are probably good ones.
although M1 is not used much anymore for the disk platform
the compression routine is still used for mass storage and for BartPE
QSC can and should yield benefits for both RIS and SysPrep platforms going forward.
i have been trying to find the potential usefulness of QSC for BartPE but i don't see it helping...
It's a good idea. This will require testers?
the double post is a frequent visitor here...
Thanks for the excellent details and your hwids.
Welcome to DriverPacks and have a great day.
ps ris is not technicaly supported but i think this is something we can resolve.
so what is the subset, machines with no floppy and no boot to usb support, as a percentage of total systems
or how many machines are new and at the same time are not new enough? lol
i am half temepted to see if it picks the unnattend file up off a thumb drive... i am curious now.
well that brings us back to your boot manager...
That is not included in our current scope... i cant think of anything obvious at this point...
so as far as i can see it is an either / or type of choice. Attended / Unattended
If you choose attended you lose any unnattended specific features.
(the install may pause for input unexpectedly - well, yeah...)
well this may not be an option anymore as much as it once was but here goes.
this option requires a floppy. windows setup will automaticaly investigate the a drive for UNATTEND.TXT
if this file exists it will be prefered to the winnt.sif on the CD/DVD.
(floppy version will be used, if it exists)
So you could have a primary winnt.sif on the ISO
and then floppys with alternate configs that you could insert at boot time.
I have read that this will work with usb devices too - but i have not done it myself.
the floppy method definately works - if you can find a machine these days witha a floppy in it
this was the method we used in the config shop. just have a floppy for each of our larger clients.
that was fast! thanks !
feature request - add support for new platform - attended setup.
can you get the hwids to us please?
errr? hmm... i did pass through mass storage on the last go
might be something to that... however, they are not sorted. so...
i can change mass storage around pretty fast now about 75% of that module is written since version 7
with the answer to that then i can code it in autoit for base.
it really doesnt matter what he writes it in.
i just need to use his logic, and that is the better half of the work.
I have forgotten how many languages i have coded, they are all the same after a while.
it is more of what our tags translate to in sysprep (having a "legend" to our map)
armed with an accurate legend it is a done deal.
there are many similarities in such as hwid and name restrictions, and many differences.
not knowing what they are puts me at a disadvantage to making it work.
Yay! we like giving back!!! woo hoo...
wow this nvidia stuff is dragging on a bit...
hmmm... i may have to dig into the packs myself.
we do update some of the included drivers - some of them dont have upgrades
we do expect that you keepthem and we will update the ones that need it with the packs.
if this was an attempt to free up space it won't help much 
leave the windows drivers in and you should be fine!
Your title should read
[REQ] Add support for new platform - Attended installation / Repair.
Good idea... I'm sure we could see this in the next release...
and described as?
unattended option;
check to optimze for full unnattended [default]
clear for the 'repair' option [attended platform support]
suggestions?
I would like to state the expectation we have always set is the unnattended disk install platform.
so if someone were to expect something that we don't support that is not our fault.
however your thoughtfulness and politeness could expand that support base.
Again your complaining that an UNSUPPORTED platform is not included.
but it should be already in the slipstreaming process as a checkbox.
No... unsupported features should not already be included. think about it... period. end of discussion on that one.
Now you are really close to talking me into adding support for a whole new platform... attended setup.
That is a whole new set of issues for us to have to support. so it is my time to code it and then support it too.
i don't appreciate the attitude that i somehow owe you or that you are entitled to anything.
you are asking me to do you a huge favor and acting like i owe you one.
I am not sure at this point i want to take on support of a group of people who aren't appreciative.
We save you time and money ask nothing in return and you have nothing nice to say.
What would you do?
you want me to spend a couple of hours at my keyboard to save you 20 seconds of your time.
and you wont even be polite or respectful or appreciative
Be Nice. (not good when i have to recommend this more than once)
Also the functionality you wish can be had by selecting only mass storage text mode.
selecting any of the other packs or selecting GUIrunonce will create winnt.sif.
although this is not a "feature" it does provide the function you require.
i could explain why this is, but i will leave that to you since you seem to have this all figured out.
well i like your approach -
you have realized that by useing the info in the ini
your progam will automaticaly update with the packs
this is absolutely the way i need to do it to add this to base. i will be following your work closely.
by you telling me what works i can add the code to base that duplicates the process.
so it probably doesnt need to be perfect - just good enough to be able to prove your method is solid.
I belive you have choosen the perfect path to the goal line.
I belive replacement drivers are an issue for you because references to the files already exist and your are adding a second reference to them without deleteing the first ones.
nice post thanks for the good details and hwid's
that will make adding them much easier...
most people use M2 but if you normaly don't that is fine too.
try it as you normaly would that way you will be familiar with the process and the result.
Thanks for testing - it is important...
now that is a nice contribution... Welcome aboard!
I agree with jaak your list of files are all OS replacement drivers (upgrades for native windows drivers)
That is where you can help us... Please test...
and report your HWID's with the results.
It is the only way we will know...
go ahead and start a topic in feature requests.
we will see what kind of response it gets.
It's a good idea...
offering a possable solution is always better than a rant...
Thanks Frants your helping to make DriverPacks better.
yes, yes and yes...
woo hoo!
these entries address issues that will hang an unnattended install.
It is much harder to add them and 90 percent of users benefit
it is easier to remove them and affects only few hundred users instead of a few thousand.
i have had many requests for this to be added...
i expect there will be posts here from them too defending keeping them.
to me it seemed deleteing an unwanted section (or the whole file)
was easier that explaining how to add the section correctly.
Feedback is what ultimately decides my path -
but i like to be asked nicely when i am working for free.
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.131 seconds, 5 queries executed ]