Search options (Page 173 of 213)

fixed http://forum.driverpacks.net/viewtopic. … 633#p19633

http://forum.driverpacks.net/viewtopic. … 633#p19633

Wim said that our host belives we are back to normal now...

Downloads should be available on our original mirrors.

hopefully this is behind us now...

no dont choose the repair option.... pretend you are going to do a clean install - jsut till you get to the selection screen..

I really don't think you are paying attention to what i am saying.

"It is very likely that reusing the same source caused some corruption of your txtsetup and dosnet files.
Especially if you made any changes to your source after driverpacks. IE adding patches / hotfixes."

by running RVM after running driverpacks you can no longer run the driverpacks again.

RVM updates dosnet and txtsetup. then when you run driverpacks the dosnet and txtsetup get restored to their original files (from before driverpacks were added the first time) this removes all entries created by RVM on the second run. (because those entries dont exist in the backed up files.)

YOU CAN'T DO THIS - IT WILL NOT WORK - this will corrupt your files.

you must uninstall driverpacks first or start with a clean source.

I make copys of my source at each stage - in this way i can update patches then make a copy and run DriverPacks on the copy. if i wish to update the packs i just reuse the copy if i must add patches i update the original and then make a new copy and add DriverPacks to that copy. In this way I can make sure that DriverPacks is always last

We state often and loudly that DriverPacks must be the LAST step in your process.

you ran RVM and driverpacks after running the driverpacks. this will not work.
(DriverPacks was NOT last in your process you ran RVM afterwards (and then DriverPacks a second time))
you can only run DriverPacks again if nothing else has been done since the last time you ran DriverPacks.

DriverPacks MUST BE LAST and your source is now corrupted and useless

what is really strange is the leech warning doesn't come up on your direct link...

Bâshrat the Sneaky is actively working on a solution...

please check out Microsoft's DPinst

this tool is now included with the RC version of base
(available on the home page - read the news artical)

with this tool it is possible to update windows with the driverpacks from a mounted drive.
hint - take a look at the DP_Install_Tool.cmd - you may not even need to modify it to work for you.

also many people use KTD to accomplish what you are doing... (the result is identical)

You did not indicate if you were adding KB921401 to your installation files?
(it updates / patches portcls.sys) and may be the root of your problem.

PS yes... your method is NOT supported

however JakeLD and some of our other regulars are sysprep gurus and may have more for you.
Personally i would rather shoot myself than use sysprep. it is awful. i have said very often on this forum that there isn't anything you can do with sysprep that I can't do without it in half the time. but I'll still help

the Request for Comments Base program 8.04.17.RC is on a different server.
go to the home page and use that link for downloading a newer base.

please use serach in future http://forum.driverpacks.net/viewtopic.php?id=521

Always include your DPs_BASE.log -
Since you did not I have no idea which version of base you are useing. I will therefore assume it is 8.04.17.RC

portcls is one of the files included in KB921401...

this may be a problem if:

you do not have sp4 installed in your source before DriverPacks

if you are useing an updater other than RVM integrator.

if you added patches after DriverPacks - then attempt to reslipstream DriverPacks.

try a clean source and report...
this may need to be addressed in the base progam (possable bug).

This can now be done easily

http://forum.driverpacks.net/viewtopic.php?id=2264

Proxy was in the RC2 release notes (below the current news item)

Thanks chiners. I know that one was of personal interest to you...

I also had confirmation from Echo_Platoon that it was working for him too...
http://forum.driverpacks.net/viewtopic. … 147#p19147

Have a great day and thanks for posting! (ps gave you the props in first post)

Thanks D!

It's fixed...