razvannh

I was having some problems with my XP SP2 install so I decided to repair it with a XP SP2 CD.The problem was that I couldn't install the driver for my GMA950. It went well, up to the point where it wanted me to point it to where the components of the driver were, said it couldn't find some files. No files were missing, that same driver kit was used for previous installs. Then it asked me if I want to continue or not, I opted NO and it went on with the repair.After a few minutes, it was hung. Tried to restart the process by resetting the machine, it kept hanging like that. Tried to redo the repair all over again; this time it asked me if I want to UPGRADE (I was already doing an unsuccessful repair) and I continued it. When it got to the graphical part of the installer, it only showed me a cursor on a black screen. Booting in safe mode gives me just a screen which says "safe mode" and nothing else seems to work. I tried to remove all the drivers which were related to DaemonTools and such from BartPE, removed all the files of the Intel GMA950 driver and I also cleaned the registry entries of the other drivers. My machine's specs: Pentium 4 Prescott, i945G chipset, GMA950 video driver The hdd is ok, checked it and it has no bad sectors and the partition is ok. I'm waiting for an advice regarding what should I do (except reinstalling, I can't do that as I don't have any means of backing up my data). Thanks in advance

After installing and attempting to slim down Vista with vLite 0.7, Windows XP crashed (not because of vLite). Around 80% of the Vista files were extracted to the temporary directory and I had to take ownership of those files in order to delete them. The procedure used to slim vista is the classic one: copy the contents of the dvd to the hdd and then try to slim it down.This is the way it worked in the previous versions. The build is 6000. Later on, I decided I should make another attempt, but I was greeted with an error when I chose the source folder and the vista edition which I want to use: " Mounting image error. Did you restart after installing the Filter Manager? / Error: -2147024784 / Anyway try restarting your computer[...]". Those files were new, because I thought the files were damaged by the failed process or something. It keeps throwing that errror, no matter what. I restarted the system and that didn't change a thing. The next thing I'll try is uninstalling vLite and reinstalling it. Thanks, Nuhi, for creating nLite and vLite!

I remember someone tried to boot windows 3.1 from an EXT2 partition and, as one might guess, it didn't boot. It doesn't matter that we have an EXT2 driver for Windows XP if we don't have a bootloader that is capable to boot windows from an EXT2 partition. The bootloader HAS to be capable to boot WINDOWS from an EXT2 partition, it has to be specifically developed to boot windows from such a partition. Taking NTLDR and trying to boot windows from an EXT2 partition won't work, taking a GRUB or LILO and trying to boot windows from an EXT2 partitin won't work either. Anyone is free to try, but some have already tried and Windows didn't boot. At least the driver for the desired partition type and a bootloader capable to boot a windows installed on such a partition type (written specifically for this purpose or a modified version of a bootloader which is licensed under GPL or BSD like GRUB or LILO) is required for this thing to work. Just putting a driver for a new filesystem in Windows won't make NTLDR boot Windows from such a partition. The fact that EXT2,EXT3, REISERFS, REISER4 or any other FS is the fastest on Linux, it doesn't mean that's certain to work under windows as fast as it does under Linux. There's no XFS driver for Windows for the time being. I will make further investigations. Information about what happens during the windows boot process would be appreciated. Grub and lilo give back the task of booting windows to NTLDR. Grub does that by chainloading it (chainload, boots windows by first booting NTLDR which actually boots Windows) and lilo does it by setting an "other" tag on the boot entry (another term for saying that it chainloads Windows).

I doubt that lilo, grub or other such bootloader will boot windows from a ext2, xfs or other such *nix-like type partition. In the first place, NTLDR has support for NTFS and *knows* how to boot windows from a NTFS partition, after the kernel is loaded, the kernel depends on the NTFS driver which handles reads/writes from/to that partition. As far as I have sought on the internet, I haven't come across such "xfs for windows driver", nor for Windows NT; that link, I presume, pointed to the SGI site, where they stated that "SGI uses Samba to export XFS filesystems to Windows NT" (that means that they use Samba to create network shares on *nix from directories on XFS partitions). Aegis, It would be a pleasure for me to beta test this minimal windows.

Not exactly what I am looking for, thanks. I'm trying to find a way of making a live cd, like a linux live cd, but I want it to be a full windows xp live cd, not like BartPE. The programs I've tested with BartPE were able to run, but they crash or generate errors. That's the reason why I am looking for a way to make a complete live cd with windows xp.

I have integrated XPize with nLite, I had to reinstall windows, some files were corrupted and it wasn't working properly.

I have used BartPE to create a few PEs, but, I was wondering if it's possible to create a live windows xp cd, that means creating an image of the windows XP install partition, make a cd and run Windows XP from it. I've done this with Windows 98, I was running it from a ramdisk (I've learnt how to this in a post here on MSFN). Given the fact that I have a Windows XP install which is as big as 300 MB, could I somehow create a live cd from it?

I made 2 kits. Both started with the original, clean, unmodified kit. The first one had only the component removal and the rest of the preset. The second, third, fourth, etc, time, I've started with the clean XP SP 2 kit and used the preset + updates on it. It was done in one pass, each time, I didn't nlite one kit twice. It's just that I didn't save those updates in the preset text file, I add them manually in nLite when I create an nlited kit. P.S. : I made such kits with nLite 1.0b4 and earlier, there seems to be an issue with direct hotfix integration. later edit: integrating XPize UAE together with RyanVM post sp2 update pack doesn't work in nLite 1.0b5 ( I haven't tried without RyanVM post sp2 update pack)

It was done all at once. This is how I did it: 1. I made an nlited install kit (and I saved the preset, it didn't contain any hotfixes) 2. I wanted to make another nlited kit, but with those hotfixes, I loaded that preset and when I got to the integrate hotfixes page I also added the hotfixes ( so, every time I create an nlited install kit with hotfixes, I manually add the hotfixes in nlite, thats' why they didn't make it into the preset). That means that the preset was created before and it did not include any hotfixes, not that the kit was nlited once and then updated!

WindowsXP-KB883939-x86-ENU.exe WindowsXP-KB890046-x86-ENU.exe WindowsXP-KB893066-v2-x86-ENU.exe WindowsXP-KB896358-x86-ENU.exe WindowsXP-KB896422-x86-ENU.exe WindowsXP-KB898461-x86-ENU.exe WindowsXP-KB901214-x86-ENU.exe WindowsXP-KB903235-x86-ENU.exe RVMUpdatePack1.2.2Lite.cab The hotfixes weren't in the preset, they were added when I made the nlited kit.

There's no issue with that preset...the reason why it doesn't work is because I have integrated some hotfixes in it. It works great without those hotfixes.

I have created an nlited install kit from a Windows XP SP2 Corporate install disc with nLite 1.0 beta 5. When it installs, it hangs during the "registering components", I have already attempted to install this a few times, I have even re-created the nlited install kit, the result is always the same, on my real PC and on vmware virtual machines. After a console appears and disappears a couple of times, it hangs during the phase when it says registering components, but it doesn't finish the install at all. [PRESET REMOVED] LATE EDIT: All of the install kits that I generated with nLite 1.0 beta 5 install very, very slow, I have waited for a complete Windows XP SP2 Corporate install about 2,5h on my Athlon XP Barton 2500+ with 1GB of RAM.