You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by RogueSpear
If you're going to remove anything with nLite, then you certainly want to use RVM first. I mainly use nLite to remove some of the more obnoxious XP items like MSN explorer, the games, and also some useless things like WordPad, Briefcase, etc.
I even made AutoImage so that it always processes RVM prior to running nLite.
Hi again
missed the order you do this in
whatever you use Nlite for, do it FIRST
then RVM
then DPS_baseNlite messes up driverpacks.
I would have to respectfully disagree with that. RVM then nLite.
How about you try the "Test Archive" function in 7-Zip?
I noticed a thread regarding this issue over in the nLite forums. Perhaps it's not totally DP related after all.
It's been discussed a few times.
Here's a shot in the dark.. maybe it's in the process of generating .PNF files - which I've found to be totally unnecessary anyway.
Well it could be possible there is an issue a non-English hotfix that would be in all non-English update packs. Although I seem to remember someone ran an install with no update pack and got this.. so maybe not.
facts are:
xp pro / home sp2 + winnt.sif + sereby´s
with base 6.086 : no desktop.ini is shown
with base 6.10 : desktop.ini was visible
XP Pro SP2 + winnt.sif + RVM Update Pack
with base 6.08.6: no desktop.ini
with base 6.10 : no desktop.ini
This would lead me to believe the problem is from one of two things:
1. Something in Sereby's Update Pack
2. Something with a non-English source (ex: unicode vs. ansi)
I hate to say this but I had the same thing happen with an Analog Devices chip today 
EDIT: One difference - the sound device was properly installed and functioning once setup was done. But again, I got the two blank cmd windows around T-34.
I really don't understand what the problem is that you're having. Why is it that ROE.exe is not working for you? I write all kinds of crazy things to RunOnceEx from cmdlines also and ROE.exe works just fine for me.
I don't know what sort of difficulties you're having with nLite, but I've been using it for probably close to two years now with no issues regarding the DriverPacks. Just for the record I use the RVM Integrator, nLite, and the DriverPacks - in that order.
I can verify this. Happened to me on a Dell Latitude recently. Except for me I just got 2 open CMD windows with nothing and then the Sigmatel was not working post setup. I have a feeling they have made some changes to their .inf file in more recent driver versions.
http://www.google.com/search?num=50&q=desktop.ini
Funny how effective that is.
The DriverPacks don't have anything to do with autologin settings. And autologon has been working for me just fine for me. I don't use nLite to manage my autologon settings, but I do use nLite 1.2RC and the DriverPacks 6.09.
Or you could just use RyanVM's Update Pack. I've been using it successfully with my RIS installations since his first update pack was released.
I also use WSUS, but I figure why not just have everything integrated from the beginning. Then when my post setup script that defragments everything runs, I know I won't have to do it again.
I've implemented a new feature in AutoImage where you can specify a saved nLite .ini file to use and using nLite's new unattended option the whole thing will run automatically now. Finally, I can have AutoImage go from start to finish without having to do anything at all.
@RogueSpear: no, THAT is the error: that an element could not be deleted from an array. Probably because an incorrect index is specified, but that's the reason for adding all those debug statements, but unfortunately they're simply not working...
Ok, I was thinking this might be an error where you get a dialog box that shows where the code is choking.
@Bâshrat the Sneaky, the error "Cannot delete element from array" is probably an error that, if it were visible, would give some more useful information that could be captured in a screenshot. Would it be possible to have the "debug" option halt execution and show the actual error dialog?
@felipe, when the DriverPack Finisher runs, is it running under a user that has admin rights? I notice from your log that you are also testing under VMware as I am, so I'm just trying to locate any differences.
']I've chosen ALL DriverPacks to be kept by KTD
and from .ini:[Settings] ; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!) DPsRoot = "%SystemDrive%" ; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! KTD = "paths:D"
@Bâshrat the Sneaky, if you select to keep ALL DriverPacks is that how the entry should appear? Or would it say KTD = "All" ?
I'm encountering the same error.
DPFinisher.ini
[Settings] ; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! (may NOT contain any spaced, if it does, all exceptions must be adapted to be compatible!) DPsRoot = "%SystemDrive%" ; DO NOT SET THIS MANUALLY, LET THE DriverPacks BASE DO IT FOR YOU! KTD = "no"
I would think the problem in this case is the KTD = "no". Wouldn't that mean "do not perform KTD" ?
I can't say for certain as I've never used that particular model, but I think some vendors are making the chassis intrusion hardware into an actual device. I've mainly seen this with rack mount servers where it hooks into SNMP for notification purposes.
Yes it does.
I've been doing this for quite some time now. It is possible to do but there are several extra steps you need to take and a few gotchas here and there as well. So I wrote a program to do it for you. Just click the link in my sig.
I've been involved with source creation for quite some time now and I can tell you both from personal experience and from reading other's stories in various forums that updating your source image in any way other than the simplest of updates is generally not a good idea. There are enough tools out there now to make the entire process not much more than a couple clicks.
Something else to consider with this - you would have to keep track of updates as they relate to several prior versions. Personally I would love it if all the tools out there did not support this constant going over the same source again and again. It would probably eliminate about 75% of the threads that have a subject line like "Help!"
DriverPacks.net Forum » Posts by RogueSpear
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.019 seconds, 5 queries executed ]