submix8c

on cd in I386 folder; all files "compressed" (eg "pinball.in_" is the INF to be "expanded" using "extract" program). 3 inf's of importance - games (, pinball, and sysoc INF's (.IN_); also "layout.inf" (not compressed). browse around in there - you'll find your answers... oh yeah, files installed are also compressed (eg pinball.ex_). this is as far as i remember... only reason i'm this "edjumucated" is because i used someone else' method of transmigrating xp games onto win2k3 (bored, i guess...).

uh, don't know if there is one. this is a boot-from-hdd, not a boot-from-cd console; might be a difference in the hal between the two... (as he shrugs shoulders...). (oh a thought... may have to do with the loader?)as i pointed out (read previous post), you can make a slipped-bootable that can be used if you need recovery console outside of hdd-boot. (no more help here... good luck!) PEACE!

ok... clueless but a tidbit of info (correct me if wrong, anyone) - the idea behind an attempted normal boot is so you can go back into safe mode immediately after, rename bootlog.txt to bootlogx.txt (just to keep it from getting it renamed if another boot with logging), then open it and look it over. last thing(s) you should find is either an error message or the last successful process (or whatever). this may help to isolate the culprit. using msconfig during safe mode and rebooting (allowing "normal" boot excluding items unchecked in msconfig) should also help uncover the culprit. using msconfig should allow enabling one-by-one each item until the culprit (the last checkmarked-item to finally fail) is found. beyond that, yeah, check config.sys (and/or autoexec.bat). obviously (or maybe not), something is corrupt or hogging the system.

??? is right! wot-tha-heck is a pencil?mine (normal start) - [386Enh] ebios=*ebios woafont=dosapp.fon mouse=*vmouse, msmouse.vxd device=*dynapage device=*vcd device=*vpd device=*int13 display=*vdd,*vflatd EMMEXCLUDE=C000-CFFF MaxPhysPage=39999The line in question is a "hex" string and nothing else should be on it... (unless of course Safe Mode/Selective Startup/Reboot is what "inserted" it... unfamiliar with the result; never use it) Oh, yeah, on a side note - FWIW, I have installed 98SE using the UBCD and used Autopatcher (on clean install). I'm using the UBCD-version now... yep, slow on startup but eventually "kicks in"... haven't figgered it out yet (looking into it now; could be "unofficial" IE6/Explorer stuff)...

go here - which os - funnyfarm (woohoo! finally figgered out how "insert topic link" works - DUH!) FWIW, IBM does the same krap for their "mainframe" OS's, so nothing new here... Yeah, started at DOS, stopped at W2K3, since my hardware is older. Any MS opsys higher than that would be just plain ignert for me to install...

@flipflop... dude! don't freak! (almost) everyone has trouble at first. i've been "yelled at" too (through a misunderstanding), so don't take it personal. you could have really screwed up and totally violated forum rules! just don't "add reply" until you are sure of what you want to say, edit the post if necessary instead of posting again (if possible), stay within your topic, and post in the appropriate forum/topic where possible. ...and try not to (which i sometimes do) "help, i'm talking and i can't shut up!" peace, bro! everyone's here to either learn or to help... edit - no need to respond to this... waste of a post, ya know...

Glad you got it sorted... To make your cd bootable, search around the internet for the CD boot file (win2k/xp/2k3, all the "same"). Reburn the CD using "iso/bootable cd" and point to the "xxx.bin" file you download (whatever the name may be) under "expert settings" (or something like that; I use Nero, similar to Roxio) and ensure Load Point=7c0 and Blocks To Load=4 (must be something similar in Roxio). Also look around on internet for better explanation (use "roxio" and/or "nero" as one of the keywords); probably will point you to the "boot file" as well... Probably will be able to find same info somewhere on MSFN; I haven't looked since I already knew... Cheers!

Only played with this for a short while (probably not helpful at all...) - The recovery partition is initially the C: drive (active partition) and the drive letters are "reversed" after recovery (C: becomes D: and D: becomes C: and Active). This "magic" is done by i-don't-know-exactly-how. Usually there is some kind of proprietary Boot code involved with recovery. I can tell you this - I "restored" a friend's Compaq back to "factory" by deleting the C: drive and setting the remaining drive to Active and rebooting. The PE Recovery Partition then allowed for a Restore. (did this because the Create Restore CD's option was gorked up and the computer was being re-sold as Factory-Reset". Any particular reason for wanting the Recover Partition bootable? The only method I can think of to "force a boot" to it is to use Diskpart to set the Active Partition to the Recovery Partition instead of the already-installed-partition... note - this was done on an XP Home PC... Vista may be a different beastie. OEM's are notorious for using "stunts" to prevent pirating in addition to MS OEM requirements...

you-gottum, dude! go for it! a final note (not relevant, but ...); just like a 9-volt battery, if you touch your tongue to both contacts, you get zapped. same thing for receptacles (assuming dumb enough to leave "live"; brother electrician did it all the time) - don't touch BOTH at the same time (oh, he was daring!). happy grounding!

Helpful hint - 1 - download and install Flashget (use the v1.73 version - it's stable) from here - http://www.flashget.com/en/download.htm 2 - go to the link given by Joe K for SP2 3 - click on the download then Cancel the grey Download box 4 - the next screen will give a Thank You with a "start download" direct link; right-click on it and choose "download using flashget" and wait for download to complete I suggest this because it will allow a large download to be saved much faster and more dependably than MS' download/save BS. Now just install it by double-clicking on the downloaded file (default save folder is C:\Downloads). P.S. make sure you have about 500MB of free space on your HDD for all of this. It very well could have been what clobbered you (aside from a slow connection?).

??? thought you already downloaded them ??? just extract the MSP's, using the most recently dated one of the same name, ignoring the older ones... Look in the Slipstream Office forum/topics for how-to's (slipstream or just apply direct from the downloaded EXE files)...

You haven't been back to say if you resolved the problem...FWIW, I had inadvertantly set "download" in Automatic Updates (I don't do that, because I like to collect and install on my own at my convenience) instead of having it Turned Off. I managed to catch it before anything installed but had to wait (grrr) until it was finished downloading. Somewhere (on MSFN) someone pointed to this - http://wiki.djlizard.net/Dial-a-fix Downloaded, ran it to clean all the garbage, and voila! back to square one ! If that doesn't fix it, yes, it could be as the others suggested. Also, apparently there is sometimes a problem at MS's server end being "overloaded". Come back and let us know if you are "fixed", ok??? edit - also found this... http://support.microsoft.com/kb/927891 fixes "hound-dawg-slow" response in Update scans...

Just a thought (haven't tried, may not work). You should have a Service Pack folder on your HDD (somewhere) containing the I386 SP2 files in it (from an Update). Copy the I386 folder from the CD (ALL of it) to your HDD (a new folder preferably) then copy the Service Pack I386 folder (ALL of it) over top of the first overlaying older (original) files ("dirty slipstream"). Then try running WINNT32 from that folder. If this works, it'll be faster than Slipstream and a Learning Curve constructing a hand-made CMDCONS. @jaclaz - I read some of the topics you linked to... good stuff, but a bit complex and I won't swear to this, but this may not give the specific result this chap was looking for (C:\CMDCONS folder with the appropriata BOOT.INI entry). I may look into the links deeper; it might be nice to make some specific intructions on how to do what this person is after... Peace, bro; you ARE good!

Sorry... request didn't help Pop still needs ya... he's more hurt than you, ya know... and ya still got him!

being slightly knowledgeable on this subject... kee-rect on all counts! be careful when changing the wall plugs... best to remove the fuse / throw the breaker (the right one, natch)... and it might be nice to purchase a "phase checker" (looks like a USB stick for a wall socket - cheap); tells whether you got the wiring right (important in sound engineering)... not actually necessary, but a good idea...

Um? I've done that before and it worked fine... interesting... in light of this -http://www.littlewhitedog.com/content-8.html so where did you get this magical "non-crossed-over" crossover cable? edit - my bad ... more info here - http://www.conniq.com/WinXPNetworking_Ethe..._connection.htm

similar occurrence for my HP USB printer. i must have it plugged-in-and-on before i boot into windows to not get the error... odd... dunno about usb stick; should work fine...

2 hard disks... got 'em hooked up rite? one primary master (at end of connector) and one primary slave (in the middle), the primary master being the one with the system on it? the message usually means that the MBR can't be found on the boot drive. last question... did you leave a non-boot floppy in the floppy drive (same result will occur)? just sounds like when you moved the 2 hard disks over, you may have accidentally put them on the cable/connectors wrong...

@Masta #2 - just remember what nitroshift said - a crossover lan cable. these are cables that have the send/receive "reversed" on one end. they can be made or purchased. otherwise, you will need an intermediary "home networking/workgroup box" and two lan cables. you cannot just connect a standard lan cable between the two. you should easily be able to find info on how to make one on the internet (somewhere). and yes you can share bi-directionally... make/buy the cable and do as nitroshift said.

Friends and relatives now gone from this disease. Miss 'em all... Just love both parents and be strong... Sent a message to the One... hope he hears...

Repost this question in AutoPatcher topic found here - http://www.msfn.org/board/index.php?showtopic=80800 You will get a quicker response within the topic rather than as a new topic.

Uhhh, VPC Add-Ons - Shared Folders - I386 is on Host: no longer shared (settings must state to "retain shares", otherwise "dropped" when reboot VM-guest)??? edit - oops; i see this is the actual OS install; better question is where did the media go? did you initiate the install from a cd-image (iso)? if so, same thing applies... (ref. nitroshift's comment)

May your Cup Of Joy never run dry!

Totally krazy and off-the-wall, but here goes... Nephew's XP-Pro complaint - "my sound quit working...". I, too, uninstalled/reinstalled the "built-in" sound card drivers. Nada! So I finally wonder "where is the Volume Control icon in SysTray?". Not there, so I go to set the "display in tray"(or whatever the tick was) to get it to show up and "sound program (or some-such) not found - install it (or some-such)". (Sorry about paraphrase... PC fixed and gone back to owner) To shorten the story, apparently the "sndvol32.exe" program was missing (somehow) from Windows\System32 folder (was still in dllcache folder). Copied from dllcache (so i wouldn't have to expand from installation media) into system32 and LO! the sound is working. DOH! So, here's my question for you: is "sndvol32.exe" in your "windows\system32" folder? (p.s. same symptoms as yours - everything "appears" ok, but no sound...)

what they said...