submix8c

Unpin/Pin? In XP?

Not sure what *anyone* is getting at? Confusion stems from this. On many occasions, clicking "Sign Out" does *not* sign me out. Very odd, but what *I* do is just open another "empty" tab and Clean *All* Browser History (Cookies and all). Seems that *maybe* the "I'm Signed In" "cookie" isn't being deleted?. Even *more* strange is the occasional (seldom) Reply that won't Post ("stuck"/ignored/sits there) because (OMG!) I've been "automagically" Signed Out. My solution to *that* one is to open another tab and "Sign In", go back to the other one and all's well again. Yes, bphlpt, there *are* some (occasional/seldom) odd goings-on and the above is how I work around them. IOW, *two* "issues" that aren't that big of a deal but *do* exist. One is "Can't Sign Out", the other is "I Got Signed Out". HTH

No. http://www.amd-drivers.com/amd-ati-graphics-drivers.html

Post what lists here? These? http://www.windowsupdatesdownloader.com/UpdateLists.aspx BTW, this is an English forum. Please use a translator English<->Spanish. For example https://translate.google.com/

Actually, your most likely problem is the fact that your running from a USB. http://www.msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/#entry922761 I've had to use this "hacked" NTDETECT even for a USB-based Winbuilder LiveXP. BTW, PartedMagic is not Windows-Based, so doesn't suffer from the affliction.

Here is the "odd" part - http://superuser.com/questions/425463/hp-recovery-partition-not-accessable-after-repartitioning Notice the order, also noting this is (usually) S.O.P. for Recovery Partitions? Notice also how "resizing" boogers the whole "matrix"? Again, the "PARTITION" Sectors ar *not* what they seem, as some of the OEM's have a nasty habit of using *non-standard* code (and "extra" sectors) thta *would* cause XP Install to "see" an odd amount of "free space", that "space" not being "seen" from the perspective of the Partition Table (as seen in the MBR), but of the Partition Sectors. Another example of "correct order of Partitions" - http://www.notebookforum.at/hewlett-packard-forum/251698311-hp_recovery-f11-bootprobleme-partitionprobleme.html A post in the thread mentioned above - http://www.msfn.org/board/topic/150419-solved-what-gives-after-4-primary-drives/#entry960025 ...and subsequent posts (HP morons follow moron Dell's fiasco...) Seriously, the Recover Partition should "never" be at the Beginning Of The Physical Drive! I just recently gave back an HP with a USB3 failure (remember that thread? Win7 x64) with nearly the exact layout *except* that the "Tools" weren't on a separate partition. FWIW, I saved that MBR and did a *complete* backup of each and every partition *and* Partition sectors in case the guy finally got a new MoBo. *And* pulled a "stunt" to obtain the Restore DVD's. (I despise these oddball OEM methods.) (Side note: thie backups I did may/may not help at all for the OP. Yet to be seen - see below.) Basically, I did this (and then some) - http://www.msfn.org/board/topic/150419-solved-what-gives-after-4-primary-drives/#entry960185 IOW, the "shrink and format" has (apparently) created a "mess", if you will ("W-Drive in Win7, but nada during Install"). Please remember (Goodells) that Dell does this same (similar) stupid stuff. ("Odd" alignments as well?) It *may* very well behoove the OP to use HDHAcker to obtain the Logical Drive starting sectors as well. Therein lies my point. Something (potentially) is amiss beyond First 512-byte Sector. BTW, not disputing the *need* for a snapshot of the MBR/PartitionTable Sector. Simply pointing out that something beyond that is amiss and that under *no circumstances* should any other action be taken other than what *you* indicate (being the more experienced). @oldtiger64 - TAKE NOTE - I bow to jaclaz' expertise. Do what he says, just read my posts as FYI's *only*.

Well, if you'd have downlaoded the SP and compared to what you downloaded (really didn't have to), you'd see that it's a typo. Yes, that's the one. I'm looking at both of them now. You know, you could have done what I just did instead of repeatedly asking.

I also noticed this - D: Partition1 (HP_recovery) [NTFS] 1 MB (11602 Mb free) <-Where, oh, where is the Recovery Data? I certainly hope that the Recovery DVD's were created before it got formatted (if it was), otherwise we (you) have an entirely different potential problem if your Win7 OS gets ge-pucked. (see jaclaz' *"peculiar" MBR* and *WARNING! Back up!* above) Although (hmmm....) since HP may have used some goofy Partition Sector code/format on it, this probably confused XP Install? (as jaclaz readily noticed in the screenshot). Edit - providing you *do* have Recovery DVD's created/ordered/at hand, then that partition is useless, as the Tools one *may* be. http://h30434.www3.hp.com/t5/Other-Notebook-PC-Questions/Delete-HP-Tools-Partition/td-p/479927 http://support.hp.com/us-en/document/c00810279 Please note (AFAICR) having (complete *and* readable/usable) Recovery DVD's allows to completely start from scratch and have the *standard* two Primary Partitions. http://ubuntuforums.org/archive/index.php/t-1403747.html

Then the premise is that the OP wishes to have Drive Letter "W" assigned as the XP System's letter when booting into (as the Running OS) to be "W" as opposed to "C"? If that's the case, then, I'm entirely incorrect. Win2K3 - C-drive (HDD0,0) WinXP - C-drive (HDD1,0) Win98 - C-drive (HDD1,1) All others "re-Letter-Assigned" (except for Win98 "hiding") the OS to match (Multi-Partitions) *other* than non-Running OS Partition (OS swap-a-doodle). Although, TBH, "forcing" a particular OS Drive Letter to have all Drive Letters *exactly* the same (no matter which OS) is intriguing. Please do carry on and ignore my interjection.

Aren't we getting hung up on the "Drive Letter" a bit too much? If (and I can't remember offhand) XP Install indeed can't "see" an x-27 Parition Type, couldn't an LiveXP/LiveLinux (WinBuilder or similar) that can allow for editing it allow XP to be installed, then go *back* and change the Types back to original value, set the Boot Parition bit back On, "fix" the MBR with Win7 CD/DVD/(whatever tool it takes), boot to Win7 and use EasyBCD to "fix" the BCD Store, then uninstall EasyBCD? Odd procedure (and maybe incomplete/incorrect?), I know, but AFAICT, the OP has formatted (incorrectly) using Win7 when the partition *should* have been created and formatted using XP Install CD. Or am I rowing a boat with large leaks in it?

(cough) XP Home Edition (cough) Seriously doubting Win2K Updates would work. Why not just attempt an install of a Service Pack, etc. and see if it blows up? After all, what do you think Windows Update would offer even with a Reg Hack? According to this, it's built on Win2000 RC, so "pre-RTM", no? http://www.betaarchive.com/wiki/index.php?title=Windows%3ANeptune%3A5111.1

re - PCI Video Cards. I will venture to say that there's a BIOS setting in it (since an "older" Socket 478) that needs "flipped" to look for "PCI First", instead of "AGP First". Some of the older ones don't "automagically" detect that you've inserted a PCI. Also betting that having *both* PCI and (functional) AGP will allow for the PCI to show up in Device Manager, although there may be Resource Conflicts. I've run into this "oddity" before. The method (AFAICR) is to insert both, flip the BIOS while using AGP, Save, Shut Down, Remove the AGP. Also (AFAICR) only really older AGP-slot MoBo's have a "jumper" instead of BIOS setting. In fact, some "stupid" BIOS actually has built-in (AGP) video and no AGP slot (built-in *is* "AGP" of sorts) but still has this BIOS setting. (memory gets fuzzy on this, but that *seems* to be the case "AFAICR"...) Here's the referenced Topic - http://www.msfn.org/board/topic/173500-ati-graphics-crashing/

Via WebArchive, right? Guess you have to get the x64 by getting the "latest" version and noting the Link to use. I've gotten both of them (from elsewhere and are correct/valid) and the "latest" one (4.7.205.0). FileHippo now completely skips the version you referenced.

You mean this - https://www.runtime.org/driveimage-xml.htm Maybe because it doesn't backup/restore Master Boot Record, only individual Partitions? You're going to have to "generate" an MBR with a tool appropriate for the OS you're restoring. Here... do a little "light reading" - http://thestarman.pcministry.com/asm/mbr/ 1 - BIOS points to ("calls") HDD's MBR where 2 - MBR is which points to ("calls") 3 - Boot Partition's PBR which points to ("calls") 4 - Bootstrap Program (e.g. NTLDR, in case of NT/2K/XP/2K3) You didn't restore the MBR, so it has nowhere to go from there. Full stop between #1 and #2.

Really off-the wall... Seem to remember an "AGP Aperture Size" problem. I had to half mine to get it to even boot. May or may not be relevant. Also, not looking back at the posts in the thread, I'm assuming the Video Card RAM is within limits of what 98 handles (unless rloew pacth "cures that?).

Hmmm... http://www.msfn.org/board/forum/89-nlite/ http://www.msfn.org/board/topic/158294-nlite-officialunofficial-faq/ Try using nLite within a temporary "Normal Installation" VM XP Install. Also - look at Screen #16 - http://xdot.tk/nliteimages.html It's not picking up on the drivers... "Safe Mode" (F8) will (usually, AFAICR) allow you to add those Drivers when it doesn't find them (in Normal Boot). Did you use the Google/Bing search? MSFN went "down" before I could post this keyboard mouse usb site:msfn.orgA "CAT" file "Filename.CAT" that's associated with a given driver. MS (AFAIK) doesn't supply those for Mouse/Keyboard/USB Drivers. (The reason I said look at Screen#16...) Also what Motherboard? You *may* need to integrate Drivers for it. USB3 Ports are particularly bothersome. Other than the above, I see no particular problems. BTW, we must have a translation problem. You said "Normal Install", not "Normal Version". We'll try to work around that. IOW, re: Picture#16, I have one Fully Unattended (for my not-so-smart daughter, including Key) but the "UnattendedMode=0" is listed/set. Sorry, I have no time/HDD Space (full)/available PC (not set up) to test this scenario ATM.

No, you didn't say you used nLite. That's why I asked. Google -or- Bing this for the (possible) answer to your problem. keyboard mouse nlite site:msfn.orgAre you using the latest nLite? You need to attach (not paste) your "Last Session.ini" file to see what you actually did. Moderators, I suggest this topic be moved to the nLite Subforum. edit - AND! Do you have "Enable Legacy USB Support" set in your BIOS? A common mistake if you didn't set that.

Could you clarify? I'm understanding you this way - "When I install from an Unaltered Source CD, the Keyboard/Mouse is recognized. If I install using *only* a WINNT.SIF/UNATTEND.TXT with *only* those items (still using an Unaltered Source), it doesn't find them." -OR- have you used nLite or *any other Slipstream/Unattended tool* to create this Unattended Install?

Um... searching yields this - https://msdn.microsoft.com/en-us/magazine/cc188782.aspx Which "kind of" says you have to build it yourself. The article previously linked only gives an explanation. I found that by looking for "GDIUSAGE". If you search for "TESTGDI" you'll find some "code" you would need to compile. Seems to be a bit of confusion there. Appears to have *never* been a download for the "TESTGDI" other than a basic explanation.

Good! FYI, there's no such thing as an AMD CPU driver, unless you're referring to the MS AMD CPU "Fix". Looks like you're done. Congratulations! Notify Dencorso to have your Mobo added to the list.

? You have an additional BOOTINI.TXT? Have you renamed something? Jaclz, since the "C-Drive" (XP) appears to be OK, wouldn't it be simpler to have the "basic" BOOT.INI plus an added line calling GRLDR which in turn has a MENU.LST that hooks to Win7? Was that the (your) initial intent? That's the way I boot my 98SE. BOOT.INI [boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="The XP and other parameters following"C:\grldr="The Windows7 MENU.LST link"MENU.LST color black/cyan yellow/cyantimeout 30title Grldr Loading Windows 7map (hd1) (hd0)map (hd0) (hd1)map --hookroot (hd0,1)chainloader +1Would that not work? (Note - those Timeout values are for me to have ample opportunity to interrupt if necessary.) BTW, the above BOOT.INI is the usual standard (along with your original line). The 30-Seconds is just to give a chance to select the Second Boot. My original XP Pro BOOT.INI is as follows [boot loader]timeout=30default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS[operating systems]multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetectC:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdconsAs you can see, I had installed the XP Command Console and changed the Timeout to suit me. This should (theoretically) be (similarly) what's in yours. It seems that all you need from here is an additional line inserted and the appropriate MENU.LST. Using the above, you would only need the SECOND entry that Jaclaz indicated. The *only* reason I flip-flopped the HDD's identity is because that's *my* entry to boot Win98SE which requires it to be the "first" HDD on the "first" partition, which is *not* your case. (sorry for the interjection - trying to clarify/help.) P.S - No, you're not all messed up. Take it slow and easy and do *nothing* beyond what jaclaz *specifically* says to do.

re: "WMI running"... OTOH, maybe any "unofficial" updates may be interfering with recognitiion of the OS? -OR- (Start reading from here down) - http://www.msfn.org/board/topic/136171-gdi-heap-extender/#entry968151 ...for some info/links referencing your RP version. Could this be interfering? (also ) Basically "COTS" (even free) naturally assume you haven't "fiddled" with the OS beyond what the Vendor specifies (both Package and OS).

Standing in a mud puddle of corrected... So... NSW tool is the best it gets? I have that laying around here somewhere...

Weird looking screenshot you have there, compared to - From jaclaz' "last one" link. Seems that WYSIWYG.

WUT???? So is anything "broken"? Nothing should *ever* be "missing" in a good/valid/complete Source. The only other cause is a Bad Burn (read errors). In the case of this Topic, the "source" is either incomplete (maybe from a "skeleton" OEM install) or it's just bogus. I give you an example of "incomplete OEM" - Microsoft's own XP-Mode VHD Image. (five year old thread)