submix8c

Did you learn this by Setting the Partition Active (one must be active) and allowing the PC to boot to it (NOT using the "F10" key )? If so, can't help much on "PC Angel"...

How do you mean "Upgrade To"? OEM XP-Pro will not upgrade; must be installed on second partition. Retail/Upgrade will Upgrade. Noted you used "Boot From CD" (runs WINNT.EXE setup) for Upgrade; dunno if that would have worked (mabe a special option? never tried it before). Usual method is boot in XP Home and AutoPlay (runs WINNT32.EXE setup); I know Advanced Options exist there. Can you boot into XP Home ok? (may or may not have "hosed" XP Home, but doubt it). If you can and everything "works", you simply have a "failed upgrade" (for whatever reason). Since you have a double-entry ("two operating systems") it may have attempted to install to a second partition that you don't have available. Boot into XP Home, open BOOT.INI (DO NOT MODIFY YET!) in the Root of the C-drive (a hidden file; in Explorer, "Tools->Folder Options->View"). You will see whether the XP Pro tried to load from a different partition there. Or just post the BOOT.INI contents here if necessary for more assistance (from myself or others well-versed in subject).

@marxo - thx, good info; made us smarter... @celtish - but still, what is asking for one? links usually contain the whole shebang and browsers usually(?) autofill(?) "http" before "www".

<snipped; no interest> A little experience in Basic, VB Scripts, DOS Batch, smattering of Assembler, HP COBOL (one of first Client-Server-oriented). Assembler, however, is my favorite.

WikiPedia "URL" http://en.wikipedia.org/wiki/URL Dunno what would ask you for a URL, but there's the definition...

Repeat - Try it... it will isolate which one is bad... simple deductive reasoning.L1 Enabled, L2 Disabled (using only CPU cache) - OK, no booms L1 Disabled, L2, Enabled (using only MOBO cache) - Ok, no booms Only one may be bad. L1 Boom, get another CPU, L2 Boom, get another mobo. Last but not least, as cluberti stated, test you RAM...

Dunno about your particular "setup", but here's my experience from a Compaq with a "Recovery Partition"... - If it's a BIOS-type Recover selection, it may need the "C:" drive to NOT exist (maybe). It will set the Recovery Partition to be Active (I think) and will cause booting into it. - If you have already been able to "boot" into (something), then ensure that the Recover Partition is the Active Partition so it will boot into it and go from there. - Lastly, usually there is an Option (in the XP you had before you blew it away) to create a Backup Set of Recovery CD's (which usually blows away the basic Recovery Stuff on the Recovery Partition). At this point you MUST use the Recovery CD's (possibly recovering the Recovery Parition as well). Loose description above (don't have access to the beast anymore, so can't confirm). Go to Manufacturer's Website for you Model (usually can enter Serial Number or such to get to your specific PC) and check around. You could also ask Tech Support there for additional assistance. HTH

Uh-uh! BAAAAD Advice! Don't think about it, leave it alone, it's ok. (tips available on MSFN/Google'ing for SwapFile Settings as well) FWIW, I still suggest "copying" the Small HDD to the Big HDD. Look around (here and Google) for info on How-To using a spare 2-connector (MOBO to Master+Slave) HDD cable and a lot of care (cover off). It would free you of the hassle of "Son Wants More Games, No Space"...

Apparently so... Here is a quote from (another reliable source) - Just a little digging around... and DOH! esdi_506.pdr - NOT used for SATA (key part is ESDI - dumb me!).

CabPack by Lars Hederer - http://www.larshederer.homepage.t-online.de/cabpack.htm I use it occasionally and like it. It uses MS' "makecab". Basically, an interface that allows any options you might use conveniently input via a GUI. States Windows 95, 98, NT4, but works on anything above Win9x/NT4 (he quit developing it). You might also want to check on MS site for "makecab" because they (did) have the package available along with some wonderful documentation giving formats, etc. You might want to do some light reading first... Thx for additional suggestions (CabTool/TugZIP). Maybe more sophisticated than CabPack? @gosh - Got the site up, eh? Looks good so far; no time to browse yet, but I will. Some links broken? Ennyhoo, thx...

Won't be a TOC on a blank, only on "burned". Does Properties display "Space Available" correctly (ref previous post) at all? On burned, will show Bytes Used GT-0 and (usually) NO space available (if not multi-session). Try installing suggested version of !@#$ Nero and try again. Ther are some patches for Win98SE (look for "Complete List of Hotfixes.." in forum) for some potential patches for CD/DVD as well.Otherwise, I too am at a loss. Maybe the burners are just "too new" for 98SE and/or Nero 6.x...

Until you set it manually, then it's moved to the root. ??? Never seen that before; OEM, Upgrade, or Clean (any version)! Always in Windows directory unless manually moved. Only one I know that puts it in Root is Win3.x...@98 Guy - You defined a 25GB Partition, therefore Windows was able to "deal" with it. If you go back to the first link I provided, there is also an "unofficial fix for GT 132GB HDD", so tryng it on a 500GB HDD wouldn't work unless it had first partition defined small enough (did you try that?). Check out the complete list of HotFixes. Also there is a WorkAround for GT 512MB RAM (the limit for Win98). Browse around in the forum for it. There are relatively recent posts providing it. Will definitely get errors otherwise. BTW Real Memory (the "sticks) is not Virtual Memory (the SWP file). Here is a quote - HTH

Also, in XP (and other NT-types?) you need to "mount" (?) the new HDD in "Administrative Tools"/"Disk Management", i.e. assign it a Drive Letter. Not sure about "auto-assignment"; don't recollect adding an unformatted HDD to my OPSYS, but just go there and check that a Drive Letter is assigned. Use "F1" key from the Desktop and search within Help for Disk Management; should tell you how to "get there from here". HTH as well...

Correct as oscardog's link states (q272620). Good call. Go here for the 98SE Hotfix - http://www.msfn.org/board/index.php?showtopic=84886 q272621 - Hotfix for bug in Reported Size in Virtual Memory Tab In list, link points to the same place; why a different "Q" I dunno. Clears that up; THX, oscardog! Go here to Fully Patch 98SE http://www.msfn.org/board/index.php?showtopic=80800 Go here for a list of additional interesting projects (but you knew that) - http://www.msfn.org/board/index.php?showforum=91 BTW, WIN386.SWP is in WINDOWS directory.

Well, ??? blah!!! I re-checked on my 98SE. Two blanks (one CD-R 700MB and one DVD+R) indicated space available incorrectly (at 650MB). Then I inserted a burned DVD-R; wouldn't even recognize it. Then I disabled DMI and AutoInsert and rebooted; it recognized it and was accessible. I then re-inserted the two blanks and space available displayed correctly. FWIW, also have disabled on 2K3. I seem to have read somewhere that this sometimes helps alleviate the oddity. Go figure... No other suggestions (from me ennyhoo) available...

Yes. All of them and all questions (you know, those with ? at the end?). Offline, in a zip, with backing, not just your "word" (want a copy of my Tech history? I want yours !). Enough here...

Ouch! But if you can boot with both L1 (on the CPU) and L2 (on the MOBO) without STOP, it implies (AFAIK) one or the other may be bad. Long shot, I know, but try disabling one then the other (leaving the opposite enabled) and see if the results differ (one BSOD, one not, but still slow). And again, documentation does not specify BIOS Cache/Shadow options; is it present in the Upgraded BIOS, or is perhaps the documentation incorrect? IBM-modified Phoenix maybe; Compaq does/did that kind of krap, blocking access to some BIOS settings. Replaced a MOBO like that because of "hidden settings", 'cause that kind of stuff stinks. FWIW, there are "trial-ware" programs on the internet that will at least reveal some of those settings if not let you (permanently) modify them; sorry, don't remember one off-hand...

!@#$ Latest Nero... Same problems with older OEM Optorite "Generic DVDRW 8xMax". My particular problem also involved the firmware (backed it up by one version; !@#$ Generic), uninstalled Nero 7.x, reinstalled last Nero6.x, problem went away. Try Nero 6.1.1.15a (last one available) first to see if it helps. Also latest Adaptec ASPI(?) as well... HTH

Don't remember exactly where, but in Gmail Help, there is a place where they give specific instructions on how to set up and what boxes need to be tick'ed. I'm only using OE6 (also using Gmail POP/SMTP) but the requirements are more-or-less the same (SSL). Go there and find it, change as appropriate, and you should be ok... HTH

Start->Settings->Control Panel->System, then "Performance" tab, "Virtual Memory" box; careful now! Usually "Let Windows Manage..." is the best option unless you may be running out of HDD space. Before you change anything, first check the current Windows\WIN386.SWP size and your Free HDD space. If you give too big/too small, you might lock up the system (correction on this statement?). Also ref. RJARRRPCGP's comment/info...BTW, good info provided. Admittedly I'm shy of in-depth knowledge of these other points... Perhaps there is a relationship (? input, please)...

If you can't even get into Safe Mode, then you are truely hosed! Otherwise, look on someone else' XP system, look at their "File Type" definition of EXE, get yours up in Safe Mode, turn off System Restore, Reboot into Safe Mode, and change your definition to what you found. Can you even get to the "Start->Run" box or "Start->All Programs->Accessories-Command Prompt" (this one should give you a "window"/"box" with a "Command Prompt"). This is kind of an important question (same as Idontwantspam's except specifically how-to)... The closest thing I can think of to "fix" the problem is at minimum "REGEDIT.EXE" (see above question). Here you could at least unload the pertinent HIVE(s), get them to another XP, load them, fix them, unload them, then reload onto yours, OR directly fix them on yours. And yes, it could be possible that some-kinda-virus could be running at start-up that re-hoses stuff (wow!); never encountered one like that tho. Loosely described suggestion given here (kind of repeats what others stated)... Really odd that a EXE will run which in turn insists on "opening" a EXE; how can that be possible (anyone?)? You could also attempt to boot from the XP Install CD (if you have one) and delete the contents of Windows\System\dllchache. Viruses love to hide there... (wild shot) Corrections/expansions anyone?

I don't recollect requesting any answers based upon creating inaccurate questions. I had already cited both outside reference and cross-reference (e.g. your own posts, ref. VMM), i.e. questioning your own answers. I may have created inaccurate answers (the opposite) and my questions have been perfectly accurate and have been totally ignored and unanswered (ref. previous post). Non-Win9x had been brought into the subject to discuss "which does and does not support multi-cpu"; this is perfectly valid and supports the suggestion that the obstacles to be overcome are numerous. I, sir, suggest that you should be the one to study the subject a bit more, unless you are again ignoring my previous posts on the relationship between IBM and Mr. Gates (source code and my former personal access to IBM's)... True; lots of modules (as I had stated). However, here is where it started (you also commented) -http://www.msfn.org/board/index.php?showtopic=98123 Notice that the topic appears to be a dead issue. Here is where it migrated to - http://www.msfn.org/board/index.php?showtopic=99663 Also apparently a dead issue. And it finally wound up here... hilarious! @eidenk - I see you never posted in those topics... Here is a link to cluster definition -http://en.wikipedia.org/wiki/Computer_cluster Yes, I had several years ago read up on the subject... and the last Mainframe I worked on was OS/390ESA on an Amdahl. I had assumed you were being facetious (need another definition?) when you suggested "firing up" multiple diskless Win9x', since it doesn't appear to be relevant (not a viable solution). Directly (opposite of indirectly) answer posed questions and the original poster will then have a solution or final answer to his/her overall request to insist on loading Windows 98 SE (specifically, BTW) under the hood of his Core-2-Duo Mobo. If you re-read the original topics you will see that this is the case... "Stubbing" is a cake-walk (in Assembler). True, I don't have specifics on, eg., VXD or WDM constructs, but I'm sure others on this forum understand the concept as well as I do. "ZAPping" (not do be confused with MSZAP) is a method by which code to be "modified" is Branched-Around/Branched-Back-To or Branch-And-Linked/Returned-From tacked-on-code, potentially NO-OPing original binaries. The modified/new code is then executed (relocatable addressing aside). Granted, a simplified explanation (used it many a time), but common since day-one of BAL. That's Basic Assembler Language; the very first god-awful-to-manipulate since computations involved adder-registers for + and - ops and register-shifting for * and / ops. Look it up; I used it when I was trained to nuke cities (back in '69, gulp)! See, I not so toopid. But, sadly, EULA, EULA, EULA!. And DON'T YOU DARE argue ZAPping with me... I will eat you alive!!! With Specifics! @ohmss006 - I'm quite sure your intentions are good. Recommend only accurate constructive criticism, suggestion, or actual code. I can't help unless I get super-smart super-fast (not gonna happen soon). I have given what I deem a "slightly educated" assessment of the subject and its feasibility. You need some real gurus, none to be found (IMHO) as of yet. Suggest looking back occasionally to see if that happens. I anxiously await the final solution as I too will someday have a multi-cpu MOBO/Server (already have NT-type opsys; not naming it...). So far, only vague relationships and possibilities. As far as "laughing", I would have (at the "I'm smarter than you" syndrome)... BTW - Careful... get ready for another flame!Come on, yay-sayers, let's get to debugging/disassembling and recompiling/patching (EULA?) or generating "replacement" modules instead; with examples! Or else point to someone who can (if not you); some support tech you would be if you didn't (I was and did)! Done tooting horns? Getting noisy again... then Chef Ramsey (of Hell's Kitchen) said "STFU and get busy, donkeys" (another analogy). That having been said...

DOH! Absolutely correct! Forgot about that one... Good call! Worked for me before.Except... shoot! Don't see that in the documentation. Bios update maybe??? Funny thing is, the BIOS update (dated 11/10/2000) indicates that this mobo is not that old (???).

??? I thought that's what I said ??? Besides, that could also be construed as "third party"...Let it go (big "sigh" here). Many alternatives to suit the individual requirements. Wishing success to such an endeavor. I too would use it...

Definitely a nifty replacement tool (glad someone else noticed it). But be forewarned that certain DOS equivalent functions yield slightly different output. This means that some BAT files (or commands eg DIR) may not yield the same results if output is fed into another process. AutoPatch for 98SE is currently detecting it as a "no-no" until the work-arounds can be obtained. Best bet (if you try it out) is to install it, revert the Autoexec.bat and Config.sys files to the originals (backed up automatically BTW) and read the HELP stuff for more info (sloooow reading). Most "standard Command.com" functions do work exactly the same.On topic, a command.com that works like cmd.exe would be better. It would allow for CMD execution instead of the 4DOS-style alternative and would retain functional compatibility for DOS-style(?) output.