submix8c

??? Won't swear to this (maybe someone more knowledgeable will dispute this) but I don't think you can nLite a Datacenter Edition, only Pro, Standard Server, Advanced Server (same applies to Server 2K3 editions - no nLiteing a DC Edition). I suggest comparing before/after slipstream of the Pro and manually do the same to the DC Edition. It might possibly work then.

1 - "JO.SYS" is the file 2 - And if the FE is bootable, then just extract the FE boot image and use it to reburn a Bootable SE (FE and SE Boot Images are nearly identical) edit - there's also a (cough-hack) to allow using an upgrade as a full (but you need a "full" key to use it)

Read a little of this for a better idea of MBR. An example of BootLoader (for Linux/Ubuntu/etc) is Grub. Search for it. In addition, you could have installed Grub4Dos (search that too) before install Ubuntu. You can't just install for dual-boot (any combination of OS) until you know how it works and what tools may be needed... I can't tell you how to "recover" your Vista installation. Maybe someone else can (jaclaz for example). Search the forum/web (button above to right of "Search"). edit - maybe this will help (searched for it right here too!). (p.s. Vista has its own bootloader too) edit - Here is how to get your Vista install back up. Then you can proceed to "fix" your setup to dualboot.

I believe (not having Vista) that you should install Linux first then (other OS). In addition, did you use a BootLoader (like e.g. Grub)? Did you install support for NTFS filesystem? You haven't specified anything more tha "Ubuntu 10" which really says not much except "Flavor+Version". My impression (and from basic experience/knowledge) is that you can obtain/build any options you want into any given "Flavor+Version". Not? Err, in addition you "stomped" on the MBR for Vista with the Ubuntu one...

OK, let's straighten this confusion out! Read this. It means what it means, no hidden meaning. And to "uninstall" a Slipstreamed Hotfix you will have to use the official MS way (which will vastly increase the size of your Install CD, unless you intend to use DVD). Note also that the best method (to be able to "uninstall") of "integrating" is to use the $OEM$ folder, as even MS' method "overlays" the original CD files. Right? In addition, I think you are confusing folks by "bouncing" between topics BTW, thanks for starting another XP vs 9x topic.

Well, I'm confused! Google yields (for "VIA VT8375") a Northbridge. Could you give the exact motherboard you're working with (not the chipset)? Also - is also confusing. Is this a 64-bit XP? KM266 chipset makes no mention of anything other than 32-bit. It sounds like a "standard mobo" to me...Besides, I'm not really sure if installing SBL drivers will make a whit of difference (I have two of those) for XP as the built-in drivers work perfectly. edit - one more thing - the Security ID thing may cause problems with the HDD in question due to the Recycle Bins and the System Restore having contents. The ID's on the PC you ran this on will be different. You can't (generally) just "pop any old XP HDD into any old XP PC" and expect it to "just work". This isn't Win9x (obviously); NT-type systems have more stringent rules.

Rule #12

? Windows Update Downloader just downloads the updates. nLite slips them in. Compatibility has no bearing (not relevant). And yes the article is correct. looks like this is a follow-on to this.

Why would you want to delete that key? (Hmmm, says me!) If this is in reference to "Not Genuine", why not just use MS' Replace Key (using the valid correct key, of course) method and revalidate? This is part of KB905474 "WGA Validation". Works fine. Unless you mean this? This is in reference to a little-known "boo-boo" on MS' part for folks reinstalling their OS using the key on the side (COA) and the OEM's "modified" XP Install CD. In essence, (AFAICR), the files in a certain version (can't remember which) were incorrect and the only way to correct it was to first eliminate references to the "bad" and reinstall the newer, thus correctly validating. Please explain your reasoning. (cough-cough).

Hate to dispute you, but Legacy simply means "All Done, In Production, Nothing More To Do Here, Move On To New Development". At least that's the general meaning in the Military. Once I was offended that the systems being maintained were called "legacy" but after the explanation was given to me, I settled down. My mistake was not "moving on", now I'm no longer involved. edit - and as for Assembler, what do you think all of the 2nd/3d/4th/nth generation languages are built upon? Machine Code never goes away...

AFAICR, "Administrator" on 9x is the "default" user upon initial "clean" install. Generally, this happens when you have a User-Id's defined, and normally "sign on" to the PC, BUT... click "Cancel" instead (now you are "Admin"). This is the bestest answer I can give (and a little lame at that...).

"Recently bought" implies OEM, of which many provide "trialware" and "bloatware". Isolate and uninstall for more freespace.

Yes, I see that - you're trying to "brute force" instead of "sidestepping". OK, I don't quite understand how the variables are "screwing up" your configuration. What "configuration"? Please explain.Everything you need to "sidestep" Windows is in the thread mentioned (without "hacking' I might add). Just start Windows, then start your DOS-Mode and proceed from there. It , in essence, "restarts in DOS-Mode" with the appropriate AutoExec and Config settings for DOS-only. When done (and to go back to Windows), "Quit" at command-line. Simple and just like "dual-boot". You can't have "two simultaneous configurations" (as you seem to be trying to do). One is active, the other isn't and the methos as shown allows "switching" between the two (as you are wanting to do anyway). As for the "sound" did you inadvertently "hack" something away? Set up according to the given link and away you go (as if you booted to DOS).

Check this topic for some assistance. (only 2 pages long - read all of it) edit - Further, you could use the method suggested by dencorso (following your own post!)

Uh, didn't you see the stickied topics?

I'd say it's conflicting with Restore, just like Norton Goback (yuck!) would "hose" the OS (particularly WinME, which also uses System Restore). Best bet would be to use it, then "shut it down" (if possible) to allow for Restore Points. Take a look at what the software is actually doing (its logs, etc.) - betcha!P.S. I find that it's "unsafe" to allow any program to "remove redundant files" as some software actually expects it to be in a different folder (or at least in the "path"). Besides, that's a rather "generic" description they give.

Well, then please explain how you "got it to work" and change the Title of this topic to "Solved".

After looking at your ZIP attachments, a further clarification (re - jaclaz) is in order. Sectors are (generally) 512-bytes long. The MBR is one sector (always 1st sector). Each PBR is as-stated above and is JUST the 1st three sectors of the beginning of any given partition (Volume, if you will). Each Partition is "pointed to" by the MBR Partition Table. Each Partition has a Reserved Area for the Root Directory. All Files and further Directory/File chains lead off of the Root. There are rules that must be followed for 16-bit/32-bit/(other, e.g. 48-bit) operations and the info is usually stored in the associated places in the HDD according to the formatter being used. It's the code/stored-info combo that's maybe confusing you. ("why this does this and that does that?"). It's the point that's been made already (albeit vaguely). Go get a Trial version of Hex Workshop - it allows to read each singe Physical Drive and each Logical Partition. Just for fun, then you may understand... (along with StarMan's great information).

Interesting... I Google what you said "General Discussions" and when I try to go to it I get "Forbidden" in IE6 but works (can go to it) fine in FireFox. Riddle me that... Maybe that's why Google can't pick up on it? (the website+)/Forum/viewforum.php?f=76 Fine in FF, but in IE6, "Access forbidden! You don't have permission to access the requested object. It is either read-protected or not readable by the server" Try it... (I think the forum has "bugs")

Hmmm, try a google on "Unknown Device Identifier", download it, and transfer to the Win98SE PC. While on the 98SE PC, remove the Network Adapter in Device Manager , and run the transferred "UDI" program. Post what it finds for the Network Card (or just attach the whole TXT output). Above assumes a method of transferring between PC's (floppy/USB/CD-RW/etc.) Something is amiss. The FTP site has file "3C90x1.exe" (v5.4) which has within it a file named "w9x90xbc.inf". It should work if selected during "find new hardware" (this is the INF to be selected, not the others). It specifically states "3Com EtherLink 10/100 PCI For Complete PC Management NIC (3C905C-TX)". Is this an Integrated LAN (i.e. LOM/LAN-On-Motherboard) and not an add-in PCI? (Where did you get the info on "type of NIC"?) BTW, the version you're using also has that in it - just that the v5.4 has more "cards" (including LOM) listed. I have both versions.

First, may I point out that you also have to "Show Hidden Devices" to rid yourself of all hardware.Second, yes, you now need a different HAL... have you tried (also) before the Repair Install pressing F5 and forcing MultiProcessor? Third, (generally, mind you) speaking, switching between MoBo's is ok as long as the chipset drivers are the same. Fourth, you may also want to disable Hibernate as well as SysRestore. Have you read the thread concerning moving a 9x (and XP) OS to a new HDD? Same/similar applies. edit (and read jaclaz' post below) - You stated in the very first post that you're moving from an Intel-chip-based Mobo to a Via-chip-based Mobo. You must remove all devices (see above/jaclaz) and do the "over-the-top"/"repair/reinstall" with minimum same SP (higher is ok). Been through this same scenario with Bro's "move HDD to new Mobo". I'll spend some time loading/moving-HDD-between Intel->Via if you wish me to prove this. Trust me, the Registry (as jaclaz points out below) stores info inside that will cause probs when "moving/cloning". Also pointing out that if the MBR is not cloned as well you will have problems (4, AFAICR, bytes stored in the Registry in Devices area).

First, 3Com has a newer version of the EtherCD (v5.4) so why you didn't go to the manufacturer... ?(dunno) Second, all you have to do is "unpack" the file and direct the Device Manager to the folder where it's unpacked. There's some INF files there and the files necessary will automatically be installed based on the contents of the INF. Just select the Folder and the INF when asked for the location of the driver. Here is the latest including documentation. edit - oops! looks like HP bought 3Com - a shame! Here... FWIW, the FTP site still exists.

"Makecab.exe" will re-compress. Mind what you were told - do in a separate folder.

??? You also got an answer here on this? Did the answers given not resolve your problems or is the problem persisting?

? Search says this is for Windows 2000... You had the same answer here. Holy Shmoly! You were given the link on MSFN! Same topic subject! Double-posting are we?