Åmbrosius

Yay Well, whatever the problem was it appears to have been fixed by the new version. Downloaded the latest one last night, burned a disc, and held my thumbs. All my HDD's are now being picked up by Setup. Woot! Can't reformat atm, have things to do (I hate working for a living) but in theory PnP is the easy bit so if it works at setup it's bound to work in PnP. In theory. Thanks Bâshrat, a great utility, now even better

Hmm, doesn't work with Method 1 either, which is probably a good thing as I have nowhere near enough space available to do it that way. Well, I've tried everything I can think of, including skipping RVM and nLite, swearing profusely and holding it out the window and threatening to drop it, without much success. I attempted, from memory, to redo it the old way in conjunction with BTS, but it got kind of annoyed with me and didn't even try to work, so I guess I really can't remember anything too well. Guess I'll wait for this mysterious new version to appear and hope for the best. Then again, I suppose it's a good excuse to upgrade my MoBo In the mean time, any suggestions would be much appreciated. Thanks again. EDIT: Okay if I download the v1.0.0.8 drivers from SiliconImage, and incorporate them with nLITE RC8, they work perfectly in TXTMODE and as a Plug&Play. Only problem with that being that then I can't use BTS for my Audio, LAN and Graphics, otherwise it disapears again. Against all docmented advice, I just tried running my image through nLITE after BTS Driverpacks have been run, just to incorporate that SATA driver, and it seemed to work without any nasty side effects, except that it then didn't install as a Plug&Play driver instead. The exact opposite of the original BTS Driverpacks problem. So, the question is, does anyone know what I'd need to change to be able to slipstream BTS's MassStorage and the nLite incorporated driver, without any scary surprises, so that it works at both points, as I'd like to avoid having to build 2 discs just so I can support the 3114. I still can't understand why everything else works, but not the 3114, as by the looks of things, the MassStorage pack version ts the same, except for the .CPL, which surely can't effect anything at the TXTMODE point, unless it's the missing .VXD, which doesn't sound right either. Guess I'm back to the global conspiracy theory then I'll shutup now, as I fear I'm getting close to spamming, and nobody seems to care about poor little old me anyway. Woe is me. I'll just camp outside and wait for the new release to come out, trust me to have a problem when everyone's busy Beta testing. Meh. I hate technology.

Okay, just tried BTS packs and they're great, thanks Bâshrat. Unfortunately my SATA 3114 doesn't get detected by XP Setup, or at any point prior to first logon. I shifted my drives around to the other controller, and when Setup has completed and logs in for the first time, all the drives can be seen, so at some point it is installing, just not during setup. It used to work fine during Setup with the driver integrated with GreenMachine's method (Which has disapeared now, I knew I should've written it down instead of saving a .lnk, and no I don't have a backup, it's been one of those weekends ) The chipset, audio and graphics all seem to be working perfectly, just not this SATA. Which is a problem since that's the controller my C:\ usually sits on, and I have a further five partitions on three discs which don't get detected until too late for half my scripts, custom drive letter allocation, shifting my doc folders etc. Anyway, I believe that your packs grant the sought after freedom from F6 right? So it should work? Am I doing something wrong? Or is there yet another global conspiracy to ensure I get problems that nobody else does? I'm currently using, in order, RVM UpdatePack 2.0.5 (2.0.6 doesn't like me ) through the RVM Integrator v1.2.2, then running it through nLite RC8 to slim it down a tad, then copying and running the contents of UWXPCD_ROOT. It's a Method 2 option build from BASE_V6034 and it's using MassStorage V6031, and all other up-to-date packs excluding Graphics B and WLAN. The offending SATA controller is a 3114 on a ABIT IC7-MAX3, HWID : PCI\VEN_1095&DEV_3114&SUBSYS_61141095&REV_02\4&1F7DBC9F&0&18F0 That's all the vaguely useful information I can think of, so I've no doubt forgotten something. Thanks for any help.

Hmm, that could be it, the only thing I've changed since my last disc, apart from a few changes to the batch file, and updated BTS, was downloading the RC6 version of nLite. I do have one theme pack integrated via the RVM integrator, which does have a copy of uxtheme in it. Since nLite gets it after the RVM integrator, I suppose it could be getting annoyed with me. I'll give it a bash after a short ciggy break, nothing ventured nothing gained, got a few other things to check on anyway. Woe is me, having to do things manually, meh thank the Gods for VMWare. Guess this is just one more nudge away from nLite, already moving my tweaks soley to reg-files, it's too annoying trying to trace two sets if I do some through nLite too. Still a pain, but easier to undo for that matter too. Anyway will go now and try shoving a copy in after everything else is done. EDIT: Nope that didn't seem to fix it. Redid the cd image with a manual uxtheme, and reinstalled. No difference. The install copy is definately the uxtheme I wanted to install, pulled off a copy and it's identical to the uxtheme.dll I wanted to incorporate, so unless I'm missing something, it's not nlite. Ran a reg file to load it on second boot, and that worked so if all else fails I'll go that route, not pretty but it may have to do. Guess I'll spend the weekend starting from scratch, doing one thing at a time, and retesting until it stops working. Yay fun. Debugging the good old fashioned way. Thanks for the suggestions though, please keep 'em coming, anything to save me from such a tedious weekend. (Especially since knowing my luck the moment I get it working, RyanVM will release the next pack and I'll have to do it all again.)

Yeah, it is patched via nLite. Even the original teletubies theme doesn't always apply automatically, surely that thing should still work? Should I revert to the original uxtheme? Or is it because the uxtheme.dll isn't being patched by nLite?

Hi all, first off I'm not sure if this belongs here or in the Customising Windows thread, this seemed more logical, but if I'm wrong I apologise. I'm here to bow to your superior intellects in the hopes that somebody can help with this problem, if it indeed exists. I'm testing an unattended XP installation on VMWare, with the latest RyanVM and BTS integrated, and a little nLite poking too. Everything works fine except that the theme doesn't apply. It's not a problem with the .theme, in theory, or with any removed components, as it works fine when manually applied afterwards, and occasionally, say 15% of the time, will apply automatically on first boot too. It also acts the same way with just the default XP theme installed. I'm assuming it doesn't always have time to do it, or something isn't happening in time. But I'm an id*** so I'm probably wrong. Is this likely to be a problem only constrained to the VM? IF not any ideas on fixing it? I've searched the forums and Google without any luck, so hopefully some of you will have an idea or two. Failing that is there any other way to apply a theme other than through Winnt.sif, e.g. batch file or .vbs that can be run on startup to ensure it has been applied? It's only a minor bug, but it's an annoying one regardless. And I only have one CDR left atm, so I'd rather get it cleared up before burning it, else I have to wait for a new cake box of CD's to arrive. Thanks in advance. (P.S. Why can't I call myself an id*** )

Just a desperate BUMP

Nope, sorry folks, that plan didn't work as planned. Still won't install because it's convinced the key isn't valid. Any more ideas? Unfortunately I cannot just slipstream the original HP OEM disc, as it flatly refuses to do so, something about already having incorporated updates. Don't suppose there's any way around that issue? The flaming key is definately valid, as I mentioned, Windows Update has already verified it's authentic, and I've never used it on another PC (Until I tried to test this slipstream of course.) My only theory now is to install with a borrowed key, then try change it post-install before I let it dial home. Problem is I've no way of testing that theory without formatting my system, which'll leave me up the proverbial creak if it doesn't work. So not an overall good plan really. Thanks for the advice so far, I knew you lot would be much brighter than me Keep it coming. PLEEEAAASE HELLLLLP!!!! Oh, woe is me :'(

Hi all, First off apologies if this is in wrong section, but it seemed logical at the time. OK, after the nightmare of repairing my WinXP SP2 installation with my OEM SP1 disc (Which didn't go too well.) I decided it was time to create a slipstreamed disc, which led me here, naturally. Firstly found out that my OEM disc wasn't too keen on being Slipstreamed, so I guilt tripped the IT manager at work into lending me an SP1 disc. Ok, to keep things simple at first, I just slipstreamed SP2. Taking it one step at a time seemed less dangerous All goes well from there, till I come to test it. It seems to work okay, up until it asks for the CD Key. The CD Key is from my OEM disk, which is definately valid. But the installer won't accept it. I, err, borrowed the key off the sticker of my office PC, and it worked fine, though obviously I can't authenticate it as it's already in use. I'm considering getting it to install with the 'borrowed' work key, then changing it to my legal one before authenticating, I'm just not sure it'll work. So to all you vastly superior intelligent folks out there, am I stuck with my original SP1 disk? Or is there something I've missed? 'Cause I sure as hell aint going to buy another key. PLEASE HELLLLP!!!! (**** I miss the old days, honestly I'm starting to think it'd be easier to hack M$ products than is to try and stay legal these days. )