submix8c

Yes, the Mitsumi MAY have caused it. http://www.computerhope.com/cdromd.htm XP Install is perfectly happy with nearly ANY drive. ALSO if you have TWO CD-ROM drives, that COULD get you into trouble. Post #31 - XP Install is perfectly happy with MULTIPLE drives. Your post is STILL confusing So, was that a REAL CD or an ISO image? You used the tools suggested? How did you "boot" from the Image? ?The Service Tag ALWAYS gives that info, even on an OLDER one (eg Dell 4600 which brother has). It will be located on a Sticker on the back OR will display in the BIOS. This would have been irrelevant to the problem since you WERE initially getting a screen, but OK, for the best (if you say so). So you DO have two CD-ROM drives in it now?Please explain or OTHER members (or internet search) will find VERY vague information about the "solution". Not cool! side note - betting it INITIALLY had WinME (from factory) on it anyway (pre-XP/post-98). Only up-to-Win2k for drivers are listed (which usually work w/XP), including WinME. The Trident MAY give problems with WinME (driver availability) .

Try this for the WUA - put this in the same folder (save as WUA.CMD) @echo off WUA.EXE /QUIET /NORESTART /WUFORCE echo Did this work? Go to Windows Update and try now. pause. exit. and double-click it. You have to read the thread to see "what's what/how/when/where/why". Not sure about the "why rename" but irrelevant. Please report back.

Answer to initial question/Topic - http://farm5.staticflickr.com/4129/5070200770_4ec7edbb53_z.jpg Don't get me started - Having a NIC connection, they STILL asked "What is your OS". Answer was "irrelevant". They didn't like the answer so I just said "XP" to continue the convo. Use CCleaner to clear it all out (regardless of browser?) and call them back. Truly, the Phone Lines (since you said ATT) could be getting "static" (electrical interference) from outside. This was the problem when I had RR-Cable (dumped it for ATT - $) after they FINALLY got a tech to "fix it". They kept insisting "connect directly to modem and reboot". Straight-forward method - http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ipconfig.mspx Then let's see them deny it...

Google convert to pdfMany/most companies accept resumes that way. I have no clue what you mean by "margins and stuff". Well, yeah, and depending the PC specs and your budget (try eBay for some older stuff - suggestions given, others found all over MSFN for alternatives, including Browsers "that work"), if you REALLY think Win9x is "dead", then go ahead and put yours out of its misery. (This is eerily starting to look like another "x Is Dead/Not Dead topic...)

Ow, Come on! IMGBURN can be used Standalone. (Google) to "extract". http://www.microsoft.com/en-us/download/details.aspx?id=38780 is also Standalone to mount the Image. Bear in mind, please, that the OP has stated No need to "install" but they are such SMALL apps, so what?The Linux will have to be mounted In RAM to allow for "eject", another subject. And what about that RAM installed. Would need a MDS LiveLinux to get into RAM (also another subject). Hey, make a MDS WinBuilder LiveXP InRam (same difference - mine pegs out with "basic useful stuff" needing 512mb.)The simplest solution is to first TEST for CD-Access via Boot Floppy (see Dell links provided). It APPEARS that that model has what's needed AND that it MAY have come "supplied" with said Video (add-in). It APPEARS also to have a ZIP-drive. The "shall we play" comment was directed at the OP, btw, and NOT as a snark. Two posts, insufficient information. and have all they need for tools to "test" and properly respond. Our "job" is currently at a standstill until then. Thx for the CD2ISO suggestion/link.

Agreed! @the OP - FWIW, you can see the "original configuration" by entering the Service Tag # (on back of tower) here - http://www.dell.com/support/troubleshooting/us/en/19/Product/dimension-4100?~srd=true&sk=dimension%204100&scat=sup "IF" the CD-ROM wasn't changed you MIGHT be able to see what Model it is (if all else fails if you DON'T want to "crack the case" open). First thing's first, though. You need to CONFIRM you CD-Disk is "ok" -AND- that (if floppy is there -AND- set to boot to it FIRST) an "alternative" floppy (e.g. an EBD) is available. BTW, the WinME Images at BootDisk is NEARLY identical to the CD-BootImage, except for the "JO.SYS" being on the CD-Rom one (allowing for the further options). http://www.bootdisk.com/bootdisk.htm http://www.nu2.nu/bbie/ Explaining JO.SYS (and an "alternative" one) http://www.nu2.nu/jo/ (Hopefully) another explanation - Confirming you CD-disk is "good" is still a good suggestion... Can be done on your XP system easily with the right tools. http://alexfeinman.com/isorecorder.htm http://cdburnerxp.se/help/data/createiso http://www.imgburn.com/ 7-zip - http:///www.7-zip.org Mounting the ISO Image (IMDISK) - http://www.ltr-data.se/opencode.html/ All of the above are free. Shall we play with confirmations? Slightly OT - Google "windows millenium" site:tacktech.comWiki - https://en.wikipedia.org/wiki/Windows_ME

Nobody here that works for a Company (a FEW do) is going to circumvent that. We have Rules. This is the best you're going to get - http://www.amazon.com/Microsoft-Office-Student-1User-Download/dp/B00B1TGUMG Go shopping for a "Retail" one, my friend. edit - Google basically reveals you need - 1 - a Hotmail Account 2 - YOUR Company/Educational "special access code" Sorry, but you're out of luck unless you are ONE of the two above.

Still, the Driver "hanging" is the problem. At Bootdisks there are variety of images with "different" CD-ROM drivers (that is APPARENTLY the problem). Either the Driver isn't appropriate for that PARTICULAR drive (yes, sometimes OAKCDROM does NOT work) or that portion of the CD is "corrupt" and hangs. Remember, the OP stated NO CD-Drive Activity light when "Setup" was selected (after hang). 7Zip doesn't open a REAL CD mounted in the REAL CD-ROM and reveal the [bOOT] folder/image. Only an ISO image (tested that and ALMOST stated what you did). The OP has no need to "suck" the ISO Image just to use 7-Zip to get the Boot Image, hence the suggestion use BBIE -OR- get "any" BootDisk Image -AND- put it ONTO a Floppy and TEST ACCESS to said PHYSICAL CD. Thus confirming the Driver (your first point) issue vs Corrupted BootImage (but HOW?), or even DIRTY CD Disk. And if it DOES "see" it using a Real Floppy (if available, OP hasn't confirmed that) then just do it from there! My first post was "the point of the test and circumvention" (providing a Floppy Drive and Floppy availability). Not trying to "confuse" anything, just suggesting (simplistically, no further explanation) a potential work-around. Yes, I have encountered a few "oddball" CD-ROM drives that "just don't work" with the "standard" OakCDOM Driver. This could be one of them and it would be real nice if we KNEW what Make/Model -AND- whether a Floppy Drive exists, otherwise this goes Topic nowhere. We have thus far "slightly"... Floppy Drive Included? http://gdgt.com/dell/dimension/4100/specs/ The "box" pic - http://pc.watch.impress.co.jp/docs/article/20000731/npdell0.jpg

I think you folks are missing the point. 1 - The OP can't start the Setup Option because it requires the CD-ROM driver to access the CD FileSystem to Install from. 2 - The OP CAN start "Without CD-ROM Support" option and get into the DOS Prompt and ALSO will not have access to the CD-ROM FileSystem. Either - 1 - The BIOS support/CD-Drive will not read/access the FileSystem (OAKCDROM is the Driver) 2 - The Image is corrupt. Please bear in mind that NORMALLY (AFAIKR) these Bootable (FULL or OEM and NOT Upgrade) CD's have both ISO and Joliet FileSystems. The Boot Image is EMBEDDED within the CD and not accessible without software to GET the Image. That's exactly why I suggested what I did "for fun" (as a test).

So, it's "hanging" in the Boot Image within the CD? (Never gets past it?) On a different PC, put the Install CD in and use BBIE (Bart's Boot Image Extractor) to get the Image. Using a Trial of WinImage, create a Floppy from it and try booting from it (just for fun). You COULD use "any" Win9x EBD (try BootDisksDOTcom) Floppy and just run Setup from that boot.

Not allowed to sell OR give away any parts on MSFN. Rescind the offer. Reload it and play with it. Hook the HDD as Secondary to your XP and scan for viruses to "clean" it. Usually, (if an OEM) the "CABS" folder is in the "Windows\Options" folder with all you need to reinstall. Just pull the folder off to "elsewhere" (as secondary HDD?) and format/reinstall. OR recycle for (around here) $5...

What, exactly, is being Modified? Can you detect that? edit - possible - BUT can't tell for sure UNLESS a "clean" XLS is placed into the affect machine and you "edit" (open/close) it and compare "binary" the differences. quick "google" says SOME kinds of trojans exist, but you need to dfo above first to tell WHAT "may" have changed, otherwise...

Confirmed! After installing all other Updates (disregarding MSRT) except KB2813170 (previous), KB2676562 (older) and KB2839229(latest), and instead using REG entries for both KB905474 (WGA Notification) and the "Kernel Mode Drivers" REG entry (see this and -X- UDC downloads), I STILL had both KB2676562 (Kernel Update/older - see link) AND KB2813170 (also Kernel Update/previous) still showing. I went ahead and installed KB2813170 (previous) and LO AND BEHOLD the KB2676562 and (naturally) KB2813170 disappeared and ONLY the KB2839229 (latest) was offered. So the conclusion is sound - Stupid MS Update "sometimes" ignores Latest and wants Superseded until installed THEN offers Latest. Now for fun - will uninstall the Superseded (previous) and install Latest. AFAICT, there-is-no-problem. edit - DOUBLE confirmed! Uninstall, MU says "two" (ignoring MSRT), install KB2839229 (latest) and all is well. (hope I didn't mix this up much) Bottom line - Use the LATEST and you'll never-ever-ever see any Superseded. http://xdot.tk/updates.html Will be creating a "post-install" set of Scripts for installing for folks that DON'T want to Integrate. FUD is a terrible thing.

This thread appears to be VERY similar to the Win9x methodology (Pure DOS vs Command Line "DOS"), which is ALSO confusing. DOS games/pgms vs Windows games/pgms requiring some sort of "special" BAT entries (depending on). Just saying (only SLIGHTLY O/T)...

@dencorso - OK, dude! I said i was testing the "theory" because I have (had) a totally clean install and am checking against WU to see what it offers. Again, strangely it offers the PREVIOUS version. I've applied all updates EXCEPT that one/those, WMP9, IE8, a REG entry for KB2709162 (all it does), MSRT (yuk!), and WGA Notifications (also can be a REG entry), and ReVoKeROOTScertificates. Went back AFTER and those are the ones that show. The "theory" is stupid MS-Updates "sees" the PREVIOUS one BEFORE it will acknowledege the NEWER one. OT - adapted a CMD script (from MSFN for Win7) to mass-update after "shuffling" some CABS form -X- UDC. So far, so good (will post in my How To Integrate). OnT - just checking the "facts"... BTW, SOMETIMES those "nasties" occur to folks that "foolishly" up and "turn off" their PC because the silly thing is APPLYING updates (AutoUpdates) due to "confusion". Instructions on how to "clean" it's "brains" are rampant... L8tr - storm a-brewing outside.

I'm sure the OP appreciates that link also , BUT

Well, just pointing out that "for some strange reason" the latest one (dencorso and -X-) wasn't offered via Windows Update "Custom" (AutoUpdates turned "OFF"). Guess I could install the one that WAS offered (the superseded - see Xdot link) and see if the LATEST gets offered. I'll do another "test case" since I'm about to mass-update a friend's PC.

Yeah, right here - http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?DocID=HT035693 ThinkCentre 8148-15U (scratch the "-15U" part. It's just a subset of 8148 series) edit - @allen2 - DOH! Now the direct link is give.

@duffy98 - Per this - http://xdot.tk/updates.html#changelog It replaced a previous update. Interestingly, I used the "Custom" option in Windows Update (on an older install) and the REPLACED one showed up in the list. One might "assume" your correct in your "assumption" that it has been pulled due to a FURTHER bug list in the KB article beyond the "Kingston" snafu. Perhaps it was found that ANY antivirus buggered it. side note - links http://support.microsoft.com/kb/2839229 http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_update/recurring-window-update-kb2839229/49ec2c6a-9682-473e-ae5c-78a609258eda http://www.errordetails.com/238894/constantly-offered-update-kb2839229 http://qnundrum.com/answer.php?q=692348 http://support.microsoft.com/kb/2813170 <-The previous one MAY be best to "back up" to the previous update/s? It seems that even THAT one had a problem. http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_update/windows-update-keeps-wanting-to-install-kb2813170/7723e68f-1cb3-4595-a495-2c5806391dd9 FWIW, take a look at P#2 of the above and find "Stephen Hogan replied on June 2,2013".

Google avg false positivesreveals AVG has a tendency to do that. If you trust it (and the exceptions you place), then I suppose go for it. Also note that AVG "conflicts" in several ways with (e.g.) SpywareBlaster and SpyBot. Wonder if Avira would work?

http://www.asus.com/Motherboards/Z87PRO/ http://www.asus.com/Motherboards/Z87PRO/#support_CPU Better (newer) board, better (newer) CPU, different socket, same basic RAM specs. Do you read these? http://www.asus.com/Motherboards/Z87PRO/#support_QVL Hmm... still shows ALL "recommended" as "(O.C.)" beyond DDR3-1600. And their recommended supported is rather more limited for the "(O.C.)" as compared to the OTHER one. So, there ya go even with a MoBo decision change. Same-old same-old... The assertions still stand, even though I missed the flip-over. http://en.wikipedia.org/wiki/Haswell_%28microarchitecture%29 http://www.cpu-world.com/Sockets/Socket_1150_LGA1150_H3.html I highly recommend you follow the Manufacturer's (Asus) suggested supported associated hardware. Be happy and OC away. Pick one Mobo or the other. Again, your cash, your choice. edit (side note) - puntoMX is also steering you in the right direction.Heed the suggestions. Funny how you disrespect me, but it doesn't matter. I tried...

Yeah, "typo" - good thing I (normally) double-check stuff, huh? You don't read well? H@ is not a chipset, it's another "name" for the SOCKET! Which in turn, leads to the second-to-last link giving MAXIMUM CPU for that SOCKET (also listed in the H2 link). The WIKI is all about DDR3, and that covers BEYOND your Mobo, which undoubtedly covers UP TO 1600, since it is NOT the "newer" Socket (see the Socket link given) and NOT the "faster". Yeah, you COULD put the faster in your MoBo, but REALLY doubt its will run any-faster-than-1600 since they will be HANDICAPPED by the CPU<->RAM speeds (didn't notice that either?).I notice you did NOT snarkily respond in kind to this which backs up my assertions. Thanks for arguing once again in the face of facts. Follow the yellow brick road.... MAX is 1600 (divide the CPU bus and find max will come to 1600 for the RAM). You have all CORRECT answers. Live with it. Crucial RAM - http://www.crucial.com/upgrade/ASUS-memory/ASUS+Motherboards/P8Z77-V+PRO-upgrades.html Shows your 1833, but so what? It fits and works? Followup ICYMI (Asus Link I gave) - https://www.asus.com/Motherboards/P8Z77V_PRO/#support_QVL Within, yes it DOES specify MANY "faster" RAM, and they also specify "(O.C.)". The CPU will never go any "faster" and you MAY "choke" with an O.C. of the RAM vs CPU (Yes, it DOES happen). Your money... go for it! Happy now? I certainly hope so...

All kidding aside, maybe it depends on whether you're in the northern hemisphere or southern, kind of like the old reverse-toilet-flush thingy. http://www.snopes.com/science/coriolis.asp I also sleep with my head to the West so the blood rushes to my head to "invigorate my brain"... OR... the HDD "spin" is like a gyroscope and position is irrelevant?

WHAT do you MEAN "can't get in" - you mean you can NOT sign on AT ALL after the "fix"? By what METHOD did you try the "fix"? HOW much did you "fix"? I gave that link as an EXAMPLE! The problems go MUCH deeper than that. You-appear-to-have-a-nasty-TROJAN! I used a LiveXP and a GOOD AntiVirus (installed on MY computer) and used Local Network Share to scan the INFECTED computer. I ALSO (while running the LiveXP) deleted the contents of ALL Temp/Temporary Internet folders. Before that, the Trojan was INFECTING the SpyBot/MBAM. You CAN use a LiveLinux as well. Easier way - Stick that HDD into a GOOD computer (freshly installed on a Primary HDD) as a Secondary with MBAM/SpyBot(v1.6 + the definitions)/AntiVirus (get a trial of Symantec - that's the one that found most of them) installed NOT CONNECTED to the Internet. THEN do a Repair Install. Then PRAY after sticking it BACK into the Original computer and RE-RUNNING! MBAM/Spybot. You'll have to do that with EVERY infected PC. TAKE THEM OFF OF THE NETWORK or risk infecting "everyone" all over again!

@bonestonne - give it up. Several of us "arrogant" (knowledgeable) members have tried with Phaenius before and no longer respond. ...and insisted we were WRONG! (...until he found out we were RIGHT - see my "dumb as a rock Sound Engineer" posts and his last post.) I suggest you do it as well. After all, you don't want to get "reported".