Nakatomi2010

Vista is radically different than the current NT iterations out there.... It's different in that it's SUPPOSED to have ALL the versions of Vista on the same peice of media, and it;s the product key which tells the media to install the various components... It's redically different because there is no DOS setup phase... While it looks like there is, that's actually a "GUI" setup mode, you can tell by the font... I if you go to the Flyakit tutorial it tells you how to integrate a version of Longhorn into it, but as for the current builds of Vista, I've not tried as it's not out yet and so I need not worry about it.... For now anyways..... I'm sure it's possible, but it's going to be a little more tricky compared to the current multiboot standard..

Have you actually opened it up and looked inside to verify that those entries ARE really in there?

Never would've guessed that that was your versioning system... **** I feel insignificant now.... Never put two and two together....

Just thought I'd let you know as it IS potentially confusing.... Below is a copy of the post on the first page..... Now, if you look closely you'll notice you said that you'd released this latest BASE (6.03.4) release last month.... Same as the release before it (6.03.3), but the release before that (6.03.2) came out this month... Just thought I'd let ya know...

Try removing: AccessOpt = Off Indexsrv_system = Off Msnexplr = Off See what happens....

For the nForce SATAs, I've found that you NEED to copy the nvchhflt.sys file to the i386 directory.. Or the file thats named closely to it.... Without this file it'll BSOD

http://ubcd4win.com/downloads.htm Says BTS Driver package download... Needs your driver packs to work though... And I seem to remember someone else saying that it doesn't work with the newer ones, but it's the conecpt I'm after... I want to understand how it was done, so that I can go in and make the needed modifications... When the dude (Little Bugger if I'm not mistaken) made a post about this package earlier he said it could be used with any PE, not just the UBCD4Win... My problem though is that I want to add driver to an already existing PE....

So, I've got a Windows PE environment based off of what I'm assuming is BartPE, and I can't rebuild it.. I DO however use some of the components it within it and as such it's become an intergral part of my AIO-DVD, the problem is though is that is does not work on all computers, no so much an issue, however it's seriously lacking in the video driver area... Was wondering if someone could explain to me how to go abouts manually integrating the driver packs into the PE environment... I DO already have another PE (UBCD4Win) which has the drivers integrated so occupying more space on the DVD really wont be an issue since using the CDimage utility they should all "cancel each other out"..... Thank you, and I apologize if this isn't the best place for it... Edit: I am aware of the utilty that'll integrate it for me, but that, as far as I can tell, only seems to work BEFORE you build the PE... In this case I cannot rebuild it so it has to be done manually....

I will name my 23rd born child after you....

I've seen it discussed elsewhere, but when I try to do it I don't get the desired results... I want to make it so that ResHacker appears in the context menu when I right click any file.... Kinda like how HexWorkshop is there..... How would I get it to appear for ALL files Title edited -- Please, use [TAGS] in your topic's title. Please follow XP Forum Rules from now on. --Sonic

Best place for drivers, in my opinion, for a 64-bit OS is http://www.planetamd64.com

Open a command prompt window and get yourself into the directory of the file you're trying to delete... Bring up the Task Manager (Ctrl+Alt+Del) End the "Explorer.exe" process, this will shut the shell down, but your command prompt will still be open. From the command prompt delete the file... If it says it's still in use then yeah... Get the unlocker program...

Can I ask why?

I typically don't bother surfing to a network destination, I've found that Windows' ability to find networked devices are a bit weak... Memorize your computer name and just navigate to it directly... So in My Comter's address bar we would type "\\ComputerB\Share\" and it'd take us directly to the thing, rather than waiting for XP to find it, you're telling it "It exists, now to there"

I understand it's purpose, but what I'm wondering is how it "works", that is to say when you tell it to do the repair in text mode, what exactly does it do that allows all the settings to stay put... I understand that you wait for the 3 screen, hit 'r', etc etc... I want to know what's going on behind the scenes..... Title edited -- Please, use [TAGS] in your topic's title. Please follow XP Forum Rules from now on. --Sonic

You're not using the right "label maker" mode.... It's under Extra Options, and it'll specifically say "Print Lightscribe Label", once you press that the "burn lightscribe label" will appear next to the printer in the menu bar, it'll be a golden disc like thingy....

Start Nero Smartstart and under one the 'Extra Tools' tab should be "Print LightScribe label" next to a lightscribe symble, this'll open up a piece of software with a CD in the middle where you create your design, you can hit the "Burn label" button up top, should show you a preview, then insert the Lightscribe DVD into the drive, data side up, and burn your label... I use Nero to burn my labels, works fine, take sabout 30 minutes...

Any idea where I can nab that 'raining' background?

I figure since this is software it should go here, if a moderator deem sit should go elsewhere go ahead and move it.... Essentialy I use Autoplay Media Studio 6 to make my Autoruns, but they look like crap, and run a little like it too, so I was wondering if some of you other people who have used it could come up with tutorials on how to get the most out of it for us little folks... Just things that let us grip how it works, and so we can improve on it...

Odd, I tried that and it didn't work.... Which .dat are you hex editing?

If I understand that correctly, then yes that's what we're trying to do... However, if you used the software to do it, what I'd like to know is how to do it manually... I've found the while having something do it for you is great, knowing how to do it manually is better because you tend to learn more about how the OS works, and the method you used there could be applied elsewhere...

No, I'm after being able to stick the CD in the drive and then letting boot straight into the recovery console. The method it's describing, if I interpret correctly is to add it as a boot option on that system. I don't want to have to make modifications from system to system, I want to be ale to pop in the CD, push a couple keys and have it boot off of any system... Currently I'm getting an error that says "Sorry, but I placed files here that aren't here anymore, so I'm not going to work" I've tried various things and I'm drawing a blank on this one....

I'm posting this here for two reasons... I figure the following information is relavent to the discussion, and since it's something I want to do, and I'm at home right now, I'm posting it so that when I get to work I don't forget where it's all located.... http://support.microsoft.com/default.aspx?...kb;en-us;307654 KB Article discussing how to add Recovery Console to boot.ini Note: When using the command displayed above in conjunction with an x64 copy of XP i386 should be changed to amd64 [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional x64 Edition" /noexecute=optin /fastdetect C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons Boot.ini after cmdcons installed... On %systemroot% a HIDDEN directory called cmdcons appears with all necesary files to start recovery console on boot from boot.ini. 64-bit directory is about 10mb, 32-bit directory is about 8mb... This concludes my 'Notes out loud', sorry if it's not a complete thought, but I intend to see what I can do with this in terms of adding it to a Multi-boot environment when I get to work... Should be around 9:30ish EST.... Edit: I'm at work now..... It would appear as though doing the command listed in the KB article above is the equivalent of copying the BT directory to the hard drive, the directory sizes and content appear to be the same... Based on this information, and looking at the boot.ini file it's ,my belief that all of our Multiboot CD/DVDs ARE Recovery console ready, we just need to be able to excute the '/cmdcons' parameter when loading the thing.... Edit 2: I can pretty much confirm now that when doing "%XPSOURCE%\i386\winnt32.exe /cmdcons" the cmdcons directory it creates IS the equivalent of the BT directory that we make when we grab it from doing winnt32.exe 'upgrade' to get it in the first place. I know this because I took the cmdcons directory and stuck it on the CD and treated it like a BT directory, so I made CMD1 directory and .dat file from a boot sector, deleted bootsect.dat and migrate.inf from the directory, then made the changes in the setupldr.bin file, and when execute it goes straight into text setup mode.... With that in mind, in order to load the recovery console from CDShell (What I use) we'd basically need to add the /cmdcons modifyer for when we execute it... Edit 3: I've got a theory on how to do it now, but my method is going to be a bit moronic in doing it because I don't know how else to do it... So yeah... Should take more than a couple moments to do though.... Edit 4:: This KB article tells us that when starting the text setup, pressing F10 instead of F6 at the time when it says "Press F6" will make the setup boot directly into the recovery console. AFTER it loads drivers and such though, so basically rather than stop and ask you if you want to boot to recovery console, hitting F10 will tell the system to just boot to the recovery console automatically when it's done...

Lately I've been contemplating making a true WinPE CD and have it autorun some file for installing Windows, so it would copy all the files to the drive and then do the install, ALL through WinPE... Would this be possible, or the setup files NEED to be copied by the text setup, and the system HAS to reboot between file copying, and GUI setup... I mean, the way I see it, it would cut down on the install time since it wouldn't HAVE to reboot the PC... I'm assuming the GUI setup IS Windows PE on the system anyways.... Would it save time, or no not really..?

UBCD4WIN is BartPE... http://flyakite.msfnhosting.com/BartPE.htm That is pretty straight forward... Worked for me, it's how I boot it, and 3 other PE's.... (Which coincedentally don't conflict with each other in the Programs directory :|