Search options (Page 18 of 58)

Err, have you actually tried it already?

Ususally, the problem solution works that way, you try something, it doesn't work, oyu come here, report and we'll see if we can find a solution.

It does not help much to ask about problems that you may expect to happen when you have not already given it a try.
If you do not have a spare machine to do a test run, use a VM - it won't install any drivers per se, but the Finisher et al will run through regardless.

if both apps use ROE and they use different IDs, you WILL BE FINE.
Don't break your head (and ours) about something that actually doesn't pose a problem IRL

Yeah, just what happen in here, it seems:
http://forum.driverpacks.net/viewtopic.php?id=2858

Just for the record, the official abbreviation is indeed OOBE, as I wrote.
OotBE would be more correctly, though, but that's MS.
Just saying because you may have a hard time finding further results if you google for "OOBT" instead...
Personally, I am doing my unattended settings via nLite - so, if you want to follow my path, I invite you do do the same (it's probably more "newbie friendly" than editing the files by hand using an editor).
Anyway, I slipstream SP3 first (or rather: use an already slipstreamed source as a basis for my U³WXPCD so I can skip that task - just be sure to have done nothing else to this backup source than slipstreaming SP3).
Any further setting are hence being applied after SP3 has been slipstreamed.
Dunno if this matters, but let's presume the Sp changes this or that, I can be sure all my editings are not being revised/overwritten/changed.

Also, always remember, DriverPacks come last, right before ISO creation

Well, I presume if you really know what you are doing (ie. it's a virgin system so no risk of losing data) and you got a lot of systems to setup but sysprep is not your thing somehow, then it can be extremely useful because it's about the last step to make setup completely unattendedly.
But you should really mark that disc (using a hazard symbol maybe ) so you don't put it into the wrong system!

http://unattended.msfn.org/unattended.xp is the better place to go for your Unattended questions.
We really are just a part of an unattended disc, namely the driver support.
Not saying that we won't try to help you, but eac hpage specializes on one aspect so to speak so you best always ask the respective experts for best results!

Yes, this can be done (for instructions see above guide/forum), however, I would not recommend it unless you are 100% sure.
Also, DO MAKE SURE that you need the user input to kick off setup ("please press any key to run setup"') as you may otherwise havok a system when you forget the disc in the drive...

That's OOBE (Out of the box experience).
Switch it off (i.e. using nLite) and you're done!
Also, you can preconfigure extended network settings with nLite.

Probabaly missing the HDA hotfix (KB888111).
Slipstream SP3 into your source and it should work.
The "scary stuff" as you call it only affected some hp (I think) systems that got SP3 installed (not slipstreamed) because the manufacturer (not MS, this time at least) messed up and included(installed drivers for devices that were not present (Intel CPU in an AMD system...), which would then mess up the SP3 installation (not integration), resulting in a BSOD.
Really nothing to fear about slipstreaming, plus it's better than installing anyway you look at it
And no, this is not normal KTD behaviour.

Well, if you already know MSFN, why do I still have to link you up to it, eh?
Anyway, all I ever do is using nLite to remove the really unnecessary things, reduce graphical effects to a minimum (classic theme, no fancy menu animations etc) while not touching the services (very sensitive area, can do way more harm than good, plus, services only run when needed and when not running do not consume RAM).
This results in about 70-80MB RAM usage on a fresh system.
Adding a couple of necessary (for me, lol) stuff including a virus scanner, it nets at about 130MB after the first reboot.
Fair enough for me, plus, you wouldn't want to run XP on a system with less than 128Mb of RAM anyway (because the rest of the components must be very old then)

Jap, especially with these pre-modded XP CDs!
You never know what kind of junk someone included and deemed cool, fun, useful or else.
Plus, they might have sneaked up a trojan/keylogger on your ass, opened some nice ports, fiddled with the DNS entries or messed up the hosts file.

Besides, ususally, you cannot use such sources as a starting point for your own customization because they aren't pure and virgin anymore (esp nLite dislikes that!).
DP integration should normally work but you don't know what it may break (previously included non-DP drivers).

Yeah, seeing as the final SP3 is out for some time now, there's really no reason whatsoever to use any of the beta/RC version anymore.
NONE.
Plus, indeed, MS only managed to include KB888111 just before going final (thankfully!)

Build ver. 5512, AFAIK (it doesn't show under System Proerties anymore since they went final...)

Err, what do you mean by CD/DVD?
The DriverPacks integrate into a Windows source of yours.
Do you want us to offer A Windows disc somehow?
I bet it wouldn't exactly make MS rejoice...

As of now, if you DL BASE and the DriverPacks, you can make your very own Universal Driver Disc - what would yours offer over the current solution?
Also, as you may know, some packs are updated quite regularly.
Having one disc image would mean to update the whole pack and make each user DL it after each and every update.
Granted, we could work with xdelta files, but still, you'd need to get the whole thing at least once.
As of now, users on a low bandwidth connection can chose not to include packs they do not deem necessary.

Also, you can already donate to the project if you like it!
If you wish, also on a per download basis

No.
RAID is only good for when you actually want to set up a soft-RAID.

If you are going to reinstall, just switch to AHCI beforehand and use DPMS.
Just DO NOT switch modes with an OS already installed, that is guaranteed to screw things up beyond all reckognition.

Thing is, the BIOS will change the PCI IDs of the controller, the OS will likely not have the drivers for those present.
You will BSOD during boot because once the BIOS compatibility mode gets switched to the proper DMA, the OS cannot load further boot files from the drive.

Ok, installation works fine so far (apart from some addon quirks as usual, but totally unrelated).

Anyway, the txtsetup.SIF file says:
symmpi   = "LSI Logic PCI Fibre Channel-Hostadapter"

So that's what the file is for.
This entry is already included in the DELL version of the CD, so maybe this is a conflict caused by the fact that a SCSI driver BASE wants to add is already present?

I really don't have any need for that driver (and seeing as it's Fibre Channel, chances that I may stuble across a system sporting this are very slim).
I'd just like to get TM support back up and running, because there is a bunch of drivers I do need for other systems.

UPDATE:

I just re-slipped the BASE using the same options as before minus TM support for DPMS (as it isn't needed on this very machine I am setting up atm).
I was using the old, non-working source btw (too lazy to copy from the backup pre-BASE ISO ).
Works so far as getting me to the partition selection screen.
Haven't tried any further yet (did put Ubuntu on it out of despair...), will do so later on.

So I think we really can reduce this one down to DPMS TM...

BTW: $OEM$ only contains cmdlines.TXT

Am I blind or is there no SC device listed???

Anyway, my money is on the missing HDA hotfix (KB888111).
Which notebook these days does not come with HD sound?

Easy solution:
Slipstream SP3 into your XPCD (you will want that anyway) and there you go.
Inlcude the DriverPacks (especially Sound) and you whould be set.

Would be surprising if this one (didn't look it up, though) wasn't using Realtek HDA...

The Dell OEM CD maybe?

Dunno, just a thought.
Will try later with my Original SP0 slipstreamed to SP2 slipstreamed to SP3 CD...

Anyway, what IS the file good for and if it's not that critical, is there a way to simply ignore it and have textmode setup continue?
Currently, I cannot get this system installed that I would very much like to finish over the weekend.

Obviously, as it only uses a standard IDE controller, I could do without DPMS (or the TM part of it), but I'd still love to solve this one for my UWXPDVD just because, you know...

PS: As for the $OEM$ folder:
I dunno what Dell put inside it but slipstreaming the SP3, nLite offered and was told to do so to remove all 3rd party changes done to the SP2 CD.
I was expecting no difference to an ordinary SP2 CD slipstreamed to SP3.

Anyway, it may include something due to the addons I include, but I have been doing so for over three years straight...

Well, unfortunately, it still didn't work for me

I now had both the symmpi.SYS as well as symmpi .SYS on the source, yet textmode would still complain about the symmpi.SYS file lacking...

Did you manage to successfully get past TM setup?
I don't know what else I could try for the moment.

Also, yes, the DPMS ini file might be wrong, I guess (because that is the only factor that may have changed between my last successful try and now), however, I have not yet had the chance to take a closer look at it (currently setting up a network printer/scanner...).
Maybe tonight unless someone else from the team beats me to it