2,401

(74 replies, posted in Other)

khan wrote:

Then which format we should follow ?

Ist Using RVM Integrator for Update Patches + Addons
2nd Using NLite for Removing Unneeded Windows Components.
3rd Driver Packs Base for SlipStreaming Drivers.

Then we can again Point out the Updated WindowXP Source folder to Nlite for Making WinXP.ISO Image file....

Am I Right ?

I actually prefer 2/1/3

first move the NTbackup folder to support
Nlite, slim it down.
remove the guided tour.. languages, unneeded keyboards
you must not go for sacrificing important stuff.
delete valuadd folder
delete docs
let it do it to it.
manually delete the migration folders in \386 (approx 37Mb)
also delete the dotnetfx folder (approx 40Mb)
that slims it down with 220Mb...

RVM integrator, hotfixes, soundfixes, and dotnetfx
I will still use RVM because I can have it do the ansi code conversion, which avoids a DriverPacks soundpack issue)

DPs_Base  method 2, all packs

result is under 700 Mb.

and then, for ISO you can use nlite or RVM.
I use DVDRW because I want extras on that disc.

Hi RogueSpear

you like the KIS principle too, eh?

I should have said, I think it won't be done (rather than it won't be simple)

thinking aloud

2klik base, have it run update before setting options.
result, update check sees what's needed.
user says NO.
goes to options
runs with older packs it knows it was good for.


2klik base, updates are allowed by user
no new base module, just finisher and increments.
gets new basexxx (mandatory) saves to user defined download folder
gets finisher for the session into working folder(mandatory)
gets increments into working folder (mantatory)
runs scripts for update=unzip + unzip /delete/adds and rezips, incremental addonpack gets deleted.
(unzip + unzip +rezip = so many seconds of time)
set options.
runs with updated packs.

updated packs tell old base it has to be updated if old base is run 8-) (paradox..)

your old copies of base and the old packs are still where you had them before you copied them to working folder.
new basexxx saved someplace by mandatory download.

I think it won't be simple.

Hi Maxximum et Khan

probably a h*ll to code. I think filtering drivers is not easy.

suppose DPsBase is run, and its update check finds a newly refreshed or newly added part in a pack what requires a few new exceptions entries for the filter in DriverPacks-Finisher.
If the finisher is not updated simultime, bad joss.

suppose further that a fix or update requires a newer base...
'edit: (if finisher has to be updated, base would have to be, for it is in its sfx.)

update, and start itselt fresh? Then get the newer increments?
edit: then you'd have to make that mandatory?

I am not a coder, but think it would not be as easy as it sounds.

OTOH, it might be really simple. I knoweth naught about coding

2,405

(74 replies, posted in Other)

I am an intel fan... the sixth was an AMD.
edit:  nforce 4 was NO issue in it, tho... sound was OK too.

in that AMD, the orig SP2 OEM home V2XHOEM_NL did not need the mass storage to see the sata on the raid chip.
:end edit

2,406

(74 replies, posted in Other)

hi
a network moderator at my regular hangout uses Nlite, and in our private rooms I told him that when I tried N_Lite to slip  RVM's post SP2 august's hotfixes, + all unpacked BT the Sneaky's driverpackss, it failed.

it went like this..
script error 6502 (or something like it....).

Nlite worked fine for doing things it was intended for.
ALL packs was probably beyond its capabilities.

my noob "haves a go at it'  txt is the KIS principle at work.

RVM (let it do what it was built for.) (Doesn't make changes to winnt.sif)

+ Bâshrat the Sneaky method 2 (if you had a winnt.sif for unattended, it would filter and add the required lines. If you don't have one, you find one with just two entries and can use the enhanced product to get to recovery console on a difficult machine...)

since then, that DVD worked for me in five machines so far.
the sixth  has that CPU thing issue.

Hi Khan

you mean.. like in incremental?

2,408

(39 replies, posted in DriverPack CPU)

Hi

same thing here.
the machine won't be allowed online yet, tho.
I'll copy the logs before I do corrections and further burn-in.

tomorrow night, I will probably do it/(test) with CPU 6.08. (I'll try get a log up before I format it again.)

2,409

(74 replies, posted in Other)

Hi
I use defaults most of the time.
I meant that when I used KTD, that I stuck to the defaults which came after I told it to use KTD.

Now, for the extra time KTD requires.
Right now, that is true. (the selected files get copied, which takes time)
I hope Bâshrat the Sneaky will soon release a version where adding the KTD option will NOT add extra time.
This could be done if the selected files get moved, and those that had to be moved do not have to be deleted.
This, if if one selected ALL, would even cut the time that was needed for deleting the D folder out of root...
Strange, huh?
But Deleting D folder also takes time, and if this new KTD method works, then it might become the preferred choice...

2,410

(39 replies, posted in DriverPack CPU)

Hi
I guess I will find out as well... This could get interesting.

Got the parts this evening, and have started to build a AMD machine.
AMD64 3800+
Mobo is a GA-K8NF-9-RH (nForce4-4X chipset. )
(RoH seems to stand for a production method that ensures no carcinogens are present in the materials ? HUH ?)

should be able to run setup tomorrow night (home improvement things to be done in daytime )

2,411

(74 replies, posted in Other)

here was a txt what desrcibed a method written by me, as a noobie.
reposted huge rewrite of this later in this topic.

Hi
I think one can avoid trouble by working with fresh folders.

When I ran the betas and release candidates and encountered a problem with one method, I would save the logs to a folder.
Then I deleted the entire content of DriverPacks folder, and unpacked the Base download to it all over again.
This created fresh base files.
Then I'd copy the driverpacks into the driverpacks subfolder, and also copy the source files to a cleaned out folder.

When things improved, I did some trials with sources I had done another method DriverPacks slipstream on.
But when I bailed out DURING a slip (lets say because I saw the path limit was exceeded), I would usually start anew, using fresh content in the folders.
I thought I'd better spend four minutes loading a fresh copy, than waste 50 minutes while running a trial setup that got botched because I made it difficult for the slipstream process.

all in all, DPsBase detects quite a few things that happened previously.
I often wondered wether I had more luck than others.
I also made sure I had plenty room on the hard disk.
((after twenty trials or so I had less than 28 Gb free on a 160 partition, so I moved 90 giga to another drive.. ))

I think you must have at least ten percent free room (a windows annoyance), plus 2 giga for the temps, so twenty percent free room is better..

I don't think folder permissions would be an issue here.

if it can not create the DPs_Base.ini, you might try unpack 6.08.6 in a fresh folder, and try again.

aha, I see the edit.
sereby on a clean one, and DriverPacks after that worked...

ah

Sereby's is like a copy of RVM's integrator in German...
I would not know wether there are bugs left in either one.

in RVM's integrator, you must click advanced, to enable the unicode to ANSI tool.
I would imagine this is the same in Sereby's.

I wonder wether this could be caused by running it on a previously used source

it looks like it had a method 1 done on it before, and/or sereby's
(which I have not used before)

the M2 I just did was done on a source where the hotfixes were slipped in with RyanVM integrator, and the last six versions I did like that gave no error whatsoever..

hi

I just ran a method 2 slip, (all packs..)

ALIIDE.org and ALIIDE.SY_ are both present here.

this makes me think you don't see the file, even when it is there...
in windows, how are folder options set?

had early shift, and a meal, so I was drowsy when I first read all this...
and then I reread...

wink

read that log.
a turion mobile.

when you ran this, did you have it run on battery?
Mobile chips go slower on battery than when plugged into their powerconverter.

Hi

yes, Bâshrat the Sneaky confirmed it would be possible to optimize the process when KTD is used.
a few days ago a kind soul wondered wether it was possible to not "copy and delete" the selected packs, but to "move" the selected packs.
The idea got a little discussion, it was clear that in a not so distant past, this might not have worked.
But, Wim thought it over, recoded and tested in his own machines, and told us it worked.
The beta testers should be able to put this to test soon.

if this works for you, you gain over 33 minutes.
others might gain as much as 8 minutes.

that made me wonder about your case.
I wonder why it takes 30 minutes to copy about one gigabyte.
in another machine's log I saw a little over 6 minutes..

an old hard disk one uses for tests might be a slow one.
but it could also be a wrong setting in the machine's BIOS, so that the drive works slower than it could work.

when finisher launches KTD process, the machine should already run the drive in enhanced mode (DMA etc), which is why I wonder what hardware your tests run on..

2,420

(19 replies, posted in Other)

hehe

I kept my finger on the T key....

2,421

(9 replies, posted in Software)

as to why?

I think he wants do do what the other guy asked about...
how to integrate driverpacks into an existing windows installation.

<Mr Watson frantically looking for Holmes> 8-)

2,422

(9 replies, posted in Software)

it is another.
look in M2.7z

2,423

(19 replies, posted in Other)

is there any way to keep the 'not WHQL' signed popup away when you do above?

1. Extract the DriverPacks to your PC, for example to %SystemRoot%\DriverPacks.


2.  kill popup

3. Execute makePNF.exe:

Code:
makePNF.exe %SystemRoot%\DriverPacks

4. Execute DevPath.exe:

Code:
DevPath.exe %SystemRoot%\DriverPacks

hi maxximum

when I run it on real testrig, 6.08.6 has been the best so far.
I see you ran 6.08.3

hi
in ravennt logs I see KTD was set to none, yet...

2006-08-26 02:53:16 : <KTD>  KTD cache location set: "G:\WINDOWS\DriverPacks".
2006-08-26 02:53:16 : <KTD>  KTD will not be applied, the DriverPacks will be deleted.