You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by -I-
question: why build a program that hacks into the process, if there is DetachedProgram - is there something that makes DetachedProgram 1 step to late to load driver path's ... im verry curious...
// helpfull links : Click
Just to be clear: i want to understand, more about this, to learn more about windows, and messing with it....
it is NOT, IN ANY WAY; ment as cirticism, because it think Bâshrat the Sneaky has done more than an outstanding job
yet another stupid question from me... (yes i know im full of those)...
when i look the the msfn setup timeline it apears to me that the setup replacement trick isn't necicairy
(but ofcource i could be (or probable am) wrong, so please explain??) ...
--------------------------------------------------------------------------------
» Text-mode Setup
1. Loads Drivers (shouldn't this read load Mass storage drivers?)....
2. Copies files required for Setup to the Hard Disk
3. Copies the contents of your $OEM$ folders to the Hard Disk // (uses with method 1 of Bâshrat the Sneaky-DP)
4. Reboots the PC...
» PRE- GUI-mode (Bâshrat the Sneaky Drive Packs initiated actions)
1 extracting driver packs
2 adding driver paths to the Registry
3 rename (original setup.exe & start setup.exe)
+ continue normal setup procedure.
» GUI-mode Setup
1. DetachedProgram executes from winnt.sif at T-39 stage // (what is this doing now)
2. Installs Devices // (here are the drivers from, the DP first needed right???)
euh... - i knew that 
-
euh no realy i didn't think about that part...
its not realy infected with any type of virus, - and remember that it posted recomendations befor to put it in %cdrom% and NOT in system32...
also you wil not have problems with your anti vir, as it will not be installed until after the windows setup process while cmdow will run befor setup even begins ... probebly even befor your lan drivers ar properly initiated ....
it will therefor not be verry likely that it will ever even be close to a situation thats dangerous to you...
unless you put it in a danger place like system32 no virus could ever take it to hide itself. (it that is what you are scared about).
sorry that i didn't actualy repleyed sooner but been rather buissy at work...
but you guys seemed to actualy have made progress ??? -
if i may be saying this. be: be sure to put cmdow in %cdrom%\OEM\BIN
lol - is this actualy the fist - dis-advantage of the compiled version against the old *shell-scripted* method, with that it was so mutch easier to ad this feature??
are you using auto-it scripts in your custom exe, -
or can you perhaps help me understand what you are doing
because than i may be able to help you .... to find a way,
THis topic is no longer neaded, and as of late the request is implemented...
i realy dont mind the work, but i hadn't seen this table before, (shame on me).
thanks for pointing this out to me. -
now i can start deleting drivers im shure id never use.
ive been using driver pack a few time now,
i kind of came to the conclusion that this method takes a long time on older machines. (or systems with less ram).
so i wondered about trmming theme down a little bit, deleting certain drivers i dont ever come a-cross like intel chipsets (i only have nvida sis or via ) remove old vga drivers but not all because i sti have tnt-2 and ati-128-rage cards. (*and goes on .........)
but what i do mis is a kind of list where de directory naming sceme is explained.
and i think it would be so perfect if future versions of any packs would contain a file with a directorie-listing.
for example
filename: directory.txt
drivertype: chipsets
N Nividia
-1 Nfore 2
-2 Nforce Pro
-3 Nforce 4
-4 Nforce SLI
V VIA
-1 etc....DriverPacks.net Forum » Posts by -I-
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.015 seconds, 5 queries executed ]