CharlotteTheHarlot

Sometimes he hits the nail right on the head. These tiny specific apps that enable/disable little features do what they are supposed to. And he was one of the early security sites that probed your IP to see what ports are open. Shields Up! At least he accomplished security awareness don't ya think? With the 24/7 threats and rampant spyware/adware/viruses we see now, it would be unfair to classify him as paranoid. See if you can find his pages on the Real Networks crapware calling home. He really took them apart. I'm sill not sold on SpinRite though. P.S. Sorry about the thread hijack! Back to your regularly scheduled debate.

I've done this upgrade on several desktop P IIIs and there is a very noticeable improvement from 256 to 640. ... (Score:5, TRUE) I second this comment. All of the WinXP first wave systems in the fall of 2001 that I saw were 256 MB SDRAM. It is true that 256 MB will work, but WinXP does not have any breathing room until 512 MB (like Win95 with 4 or 8 MB). The consequences are mad disk thrashing as application images are swapped in and out of RAM. At the very least it is an unkind thing to do to your HDD! If you are not doing heroic feats of computing (video editing, etc) once you get to 512 MB the bottleneck moves elsewhere (the CPU and HDD for example). At 256 MB, on WinXP one must at the very least disable Disk Indexing, leave the swap performance at Auto and also drink heavily to have any chance to keep your sanity! EDIT: removed ConservativeSwapfileUsage. Doh!

Bad uninstaller, bad uninstaller. By any chance do you have a registry export from before that uninstaller was executed? If so it is a simple matter to restore the fonts registry key. Any physical font files that show up missing but are referenced by this good registry key can easily be restored later. Actually, this is one time that even an old registry export will be usefiul. Particularly if it precedes the installation of that game. Try to find one (an existing registry export from your machine). If you cannot, then we could whip a generic Fonts registry key that includes the default font references for WinXP after a normal install. On a side note, be sure to scold this programmer by sending the company some emails. Accountability is necessary. I know that I would be angry.

Certainly you are positive that there is no phishing involved here, the emails are legitimate? Having said that, is there no way to spoof the user agent when using Netscape or Mozilla? There must be a Netscape/Mozilla guru somewhere that found the registry hack. What about the Win9x compatible Firefox 2? Surely it must be acceptable to them. Firefox 2 for you would be an easy update with no learning curve. One thing I would try now since it is easy and will not disturb your existing browsers is to install Opera, and then customize the status line on the bottom of the screen and add the drop-down box that has selectable user agent strings (MSIE/Firefox/Opera) and test all three with those sites. At least you will know what browser is acceptable to them. Is this one of those Dimension 8400's? I have a couple of them and think for their timeframe were some of the better systems from Dell (but I agree that homemade is always better). The good thing about them is that they have an excellent BIOS with respect to the disk dive sub-system, particularly SATA. You can easily put four different SATA drives in there with four different operating systems and then easily enable/disable any/all for a low-tech but 100% reliable multi-boot scenario. This means you could install a SATA on one of the four channels and install WinXP and Firefox 3 on it (if it is certain that those websites will not work with earlier Mozilla). Then you could enable that drive in the BIOS and boot to it only when you need to access your online accounts. For those other times, you just enable another SATA drive. To share data between these mutually exclusive system drives, you might just put a big FAT-32 formatted PATA drive in the Legacy ATA channel (in place of one of the opticals). This drive would always be enabled and any booted operating system would be able to use it.

Where would you do this? I did this myself 5 years ago (October 2003) by testing out Steve Gibson's Dcombobulator. It simply changed two values in the registry: [HKEY_LOCAL_MACHINE\Software\Microsoft\Ole] ;;;"EnableDCOM"="Y" "EnableDCOM"="N" [HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc] ;;;"DCOM Protocols"=hex(7):6e,63,61,63,6e,5f,69,70,5f,74,63,70,00,00 "DCOM Protocols"=hex(7):00 The commented values show what they were prior to the change. As usual Steve Gibson has a detailed description and history of the theory behind Dcombobulator here.

Among my clientele this has to be the single most common question that pops up. My standard reply: Are you computer hardware savvy? If yes the best solution for accessing images from a camera is to obtain a USB based multi-format so-called all-in-one card-reader (like $10). This will allow you to access almost any digital photo in its stored-on-disk state, which more often than not is its highest quality native RAW format (unless the camera owner messed with the menus and set it to store gazillions of low quality images). The memory card is removed from the camera, inserted into the reader and is treated like a giant floppy disk. Most file manager style programs will browse this memory card and let you copy files from it (they will let you do more actually, but I suggest only copying from it and then placing the card back in the camera and use its menu for format/delete to avoid problems). Then the question becomes internal or external? If you are on Vista, IMHO either works fine. The same goes for WinXP to some extent with some possible USB conflicts on older service packs, stick to external IMHO. On Win9x, although I know there are some members here that do otherwise, I never use internal card readers to help streamline the bootstrap by eliminating un-necessary drive letters (I only let USB devices load when I use them (on-demand)). Stick to external readers on Win9x, which fortuitously are more inexpensive and portable. To make these readers work in this manner on Win9x you must first fix up the USB sub-system BEFORE connecting the reader (and cameras). Read through and understand the massively enormous NUSB thread here. Download the NUSB package at AXCEL216 / MDGx. You may also need to supplement this with the WinTricks/Lexar package. These updates are best done with no USB devices attached! One optional final step I recommend after USB has been fixed up is to attach your card reader, and then go into device manager and change its extra drive letters to higher ones to like R: S: T: etc, so that in the future the cards will be seen under predictable drive letters. If you are not computer hardware savvy, those previous steps will be daunting (in this case IMHO you would be better served by being on WinXP or Vista anyway). The only other solution is to fall back upon the camera manufacturer's interface and subject yourself to the likely crappy software that they provide. In this scenario the camera is attached via USB cable AFTER their software is installed (and had made whatever god-forsaken system changes!) and communication is driven by the on-board camera firmware. This is where you appear to be now. If you want to continue on this path you will need to first uninstall the camera software. Then I would still consider installing NUSB and WinTricks/Lexar. Then if you must, install the camera software again and it should now correctly add this camera to the registry. P.S. I just thought of one other thing, search your Windows folder and below for occurences of Ntkern.vxd. There should be an updated one in Windows\System\Vmm32 that shows 4.10.2223. If not, you will need to run a specific Firewire update, even before the NUSB and WinTricks packages.

There are two very important reasons to NOT install plain WinXP anymore (no service packs, aka SP0, aka Gold) and, to NOT install WinXP with only SP1 ... * SP1 enables 48 bit LBA addressing for drives larger than 137 GB. Your 48-bit aware BIOS is not enough by itself. To cut to the chase, WinXP without service packs is comparable to Win9x in this regard and is not safe with any HDD larger than the usual 120 GB retail drives (regardless of how many partitions one creates). Note: this is absolutely true for PATA drives, but there are still mixed opinions on SATA and USB adapted drives. Microsoft is of no help to us here as usual, so I say: play it safe and assume no large drive should be used prior to SP1. * SP1a does away with the Microsoft Java Machine (call this the post-lawsuit service pack). Since Java apps are ubiquitous these days, and since MS Java was their failed attempt at a Java Runtime client to support all those Java apps, installing any WinXP prior to this service pack may install or allow the eventual installation of MS Java which you do not want. It can be poison to modern Java apps like Yahoo IM or even Opera. On a side note, do not try to install Aol 9.0 (and probably many other apps) on WinXP prior to SP1a either as they will likely plop the MS Java onto your system (if it is not already there). The Sun JRE Java Runtime is now the proper base for Java apps. SP2 and SP3 have a long list of reasons to be installed, and very few reasons not to. But if you must skip them for whatever reason you should not skip those first two! If you have a SP0 or SP1 disc, slipstream it with the later Service Packs. There are countless threads here and elsewhere to guide you through it. My advice is to use SP3 as your minimum nowadays. The post-SP3 updates are piling up now and even a fresh SP3 install gets tons of hits on WindowsUpdate. Not I Sir. Then who Sir? Number two Sir. Not I Sir. Then who Sir? Number three Sir ... Sorry, an old drinking game comes to mind for some reason everytime I see that question.

Thank you. Ok; so - bottomline - as long as I got no errors when copying there is nothing to worry about? If you want to be 100% sure you copied all the data you should compare the source and target folders (Windiff, Examdiff, etc). However, if that is impossible because of many gigabytes, then check the source and target properties and make sure both the quantity of Files and quantity of Folders exactly match (not 100% proof of course, but pretty good). It is less likely but entirely possible that there are NTFS file permissions set or really stringent 3rd party security utilities running that effectively block casual file copying. Totalling up the number of Files and Folders before/after would show that something of this nature is in play, even if your file manager/copier/application fails to show an error. As JohnDoe2 mentioned, bytes (or more specifically disk spaced used) cannot be compared across dissimilar allocation systems. Even though practically every disk partition starts with sectors that are exactly 512 bytes in size, the formatted file system on a storage device from a Windows OS sets the minimum allocation unit (cluster size) to contain some multiple of sectors. Just considering the Fat16 / Fat32 / NTFS universe, a given cluster may contain an amount of sectors equal to 1, 2, 4, 8, 16, 32, 64, 128, 256, 512 (depending on the OS and total amount of sectors). That translates to anything from 512 bytes to 256 KB minimum allocation unit (albeit some of those are uncommon). So, any given file of exactly x bytes will actually be a different size on disk for each of those ten possible file systems (with an increasing corresponding amount of slack space disk waste as well). But to make a long story short, if your source and target destinations are not using identical cluster sizes, file sizes in bytes become absolutely meaningless.

You must mean two disk controllers. Anyway, another large assumption now (please correct me if I am wrong) ... C: is HDD with WinXP System on Primary Master (PM) D: is CDROM on Primary Slave (PS) E: is DVD on Secondary Master (SM) F: is HDD on Secondary Slave (SS) G: is the USB Drive when attached(?) Also, none are SATA? On a side note, you may want to consider chucking both optical drives for one new DVD Writer (Pioneer is like $25 at NewEgg). It will save you some power and noise, and having a free ATA position makes popping in a drive (like in this exact circumstance) much easier! Anyway, assuming this information is correct, with minor editing to my previous post (in this color), the process is ... * Disable the USB drive (disconnect it). Power down and disconnect the secondary channel devices (but leave them where they are physically): this is done by pulling the ribbon cable from both the DVD drive E: and HDD drive F:, and also pull their 'molex' power cables (please diagram the current cabling positions first). Close it up. Reboot and test that WinXP still works and make sure that no system files are now missing. This precautionary step is to verify that HDD F: and the USB HDD are really just data/storage drives. Reboot a few times (the Drives are still disconnected). Once you are certain you can operate without those drives attached then you begin ... * Obtain the Seagate CDROM and set it aside. Make sure either your current C: or your new HDD (future C:) is a Seagate. Enter the BIOS (Dell is usually F12 or ESC or F2 or F10), enable boot from CDROM, and make the CDROM first in sequence. First note the current settings! Save BIOS Settings (Reboot). In Windows, pop the CDROM disc in, cancel autoplay (if it occurs) and then shutdown. * Leave the C: where it is, attach your new HDD *** Here is how I would do this. I would not mount this HDD yet since it is destined to replace the current C: drive. Since you still have the secondary channel ribbon cable attached to the mobo but disconnected from the drives, and those two 'molex' power connectors are also free, with the case open I would just plop the new drive down right next to the computer (on a few books for height), set the jumper on this new HDD for MASTER or SINGLE, attach the ribbon cable END POSITION connector to the HDD, attach the power connector, and perform the Cloning: Power up and make sure that the Seagate program (actually Acronis) sees both drives. If not STOP!. If so, the Cloning fun begins. * When done, this new HDD will simply physically replace the one that is currently drive C:. NOTE: you can not leave the jumper on SINGLE, it will have to be MASTER with slave present (read the label and website docs). Once the old one is out, and the new one is in, re-attach the secondary devices (check your written diagram), button it up and power on. Catch the BIOS (btw, on Dells it could be F12 or ESC or F2 or F10). Change the boot order back and also disable CDROM boot (if that is what you originally had written down). It sounds bad but it is simple really. One hour and WinXP is transplanted to a newer, faster, bigger disk. The old one can (and should) be stored away for an emergency such as fire, theft, defective new drive or fatal virus attack. You will be able to revert to that exact point in time that the old HDD was replaced. Note, I glossed over the care and handling of this hardware, static precautions and other obvious care must be taken! If you have any doubts or questions you should ask them before you proceed. Others please feel free to chime in as well!

To the quoted assumption, the answer is YES, the cloning procedure is done without the D: drive present. However, to be safe, I would get a little more specific in detailing your current configuration and, where you want to end up. You have implied that the external HDD is the backup drive but did not say if it was USB or extenal SATA. Assuming for now that you have two HDD's in typical configuration, C: and D:, where C: is the Windows XP System drive, and D: is on USB (***), I would proceed in this manner .... * Disable the USB D: drive (disconnect it). Reboot and test that WinXP still works and make sure that no system files are now missing. This precautionary step is to verify that D: really is just a data/storage drive. Many times I have seen situations where WinXP becomes spread onto more than one HDD because someone installed a critical program on D:, or executed a .INF there, moved their swapfile, temp internet folder or any number of things. Reboot a few times (D: is still disconnected). Once you are certain you can operate without D: attached then you begin ... * Obtain the Seagate CDROM and set it aside. Make sure either your current C: or your new HDD (future C:) is a Seagate. Enter the BIOS (Dell is usually F2 or F10), enable boot from CDROM, and make the CDROM first in sequence. Save BIOS Settings (Reboot). In Windows, pop the CDROM disc in, cancel autoplay (if it occurs) and then shutdown. * Leave the C: where it is, attach your new HDD somewhere (master/slave jumper check). Power up and make sure that the Seagate program (actually Acronis) sees both drives. If not STOP!. If so, the Cloning fun begins. Before doing the cloning read their handy PDF manual from their DiscWizard webpage. You should first read through the thread here at MSFN called Restoring a System Backup ... and see my post #5 and post #9 which includes some detail. But before you go further, outline your hardware in more detail! Too many assumptions here! (***) NOTE: I usually advise folks to re-letter any USB HDD's and FlashDrives and all CDROM/DVD drives to higher drive letters like U: (nice for USB HDD's); K: and T: (Kingston, Flashdrives, Thumbdrives); V: and R: and W: (DVD, Read, Write); while reserving D:, E:, F: for Hard Disks and their partitions on PATA/SATA channels. This is best done immediately after using such hardware for the first time. Changing the letters later can break programs naturally.

Read my post #14 here ... Clean up Extremely bloated (27GB+) ... This method preserves the existing Windows installation (no re-install), all programs and data gets carried over without changes. If you want to re-install Windows, this method is not your solution. NOTE: some hardware expertise is required, specifically the handling of harddrives, cables, jumper Master/Slave settings, entering and changing the BIOS, etc.

This is a follow-up to my post #55 above. Now using Opera 9.62 with the same Java JRE 1.6. I need to quote myself for it to make sense ... Absolutely convinced of this speed improvement now. If you are still on 9.5x, you should upgrade immediately. Speed-wise, 9.5x feels like a buggy beta version. 9.6x feels like 9.2x. Whoops, I spoke too soon. The loooong delays appear every now and then after you save a webpage to MHT. It effectively freezes up all instances of Opera while the MHT is being created. It appears to be almost random but if I was pressed to give an estimate, I would say say this occurs about 5% of the time. Well this problem is still here but I believe this is not Opera related after all. The subject is under active discussion at this thread here at MSFN: periodically being logged out. Confirmed here, and the same thing happens to me opening any file assigned to Opera (in this case HTM and MHT). Double-clicking them without first having Opera running causes the error. It hasn't bugged me to the point of research yet. I've been dodging this error the exact same way as you and it works. Just open Opera first. But I will be watching this thread hoping you guys come up with more ideas about this. Opera 9.62 is acting the same as 9.61 and 9.60 and probably every previous version since Java JRE was required. It's a minor pain (just close the Error MessageBox) but I think we'll eventually crack this one. I noticed this as well, but I thought it was since the later 8.xx versions. I could have sworn it was present in all the 9.xx versions. It is too sporadic to be reproducible. What would be a nice fix here is to auto append to a log file all the download transactions like GetRight does. I also notice that every so often (perhaps 1% of the time) a file is corrupt even though it successfully downloaded. Having said that, I doubt I have downloaded enough files in 9.60 to be able to state with certainty that the problem is still existing. The Transfers window is definitely buggy and is acting the same as that comment above. I started a thread over at Opera about the corrupt downloads: Transfers ... 'DONE' sometimes means incomplete and would like to invite anyone with similar experiences to add to the discussion. This will wind up in a bug report. Yeah, you still have to follow those instructions to get the non-MSI Installer version of the file. No big deal, just a bunch of extra clicking.

@whatever420 ... Just wanted to follow up on my post #13 above in which I originally replied to this quoted post of yours. I commented out everything in the [ModuleCompatibility] section in Win.ini back on 4-October (about 50 days ago). No problems or differences noticed at all. Thanks again for finding that.

Poke around this server for lots of Nero goodies. Pssst, its a secret ;-)

Hey folks. I'm on my Win98se master system now. It has my largest Win9x registry of all, currently exporting at 19,540,597 ASCII bytes. The binary SYSTEM.DAT is 12,267,552; and USER.DAT is 3,375,136. This one is highly tuned and manually cleaned and there is no waste. Currently it has just 512 MB RAM although when I can spare them I often up it to 1024. The RAM is the deciding factor as to what the registry "OUT OF MEMORY" (aka "too large to fit in memory" or "insufficient memory...") tipping point is, and as far as I know there is no calculation to easily determine this as subkey complexity is also a factor. I've had exports of around 25 MB but I cannot remeber how much RAM was in the box that day. Keeping exports under 20 MB is an arbitrary discipline on my own part based on long experience and some intuition. HKCR will typically take up one half the total size. Here is what I just exported: 9,119,507 bytes in CLASSES (the only real advantage to WinME should be obvious, it would be nice to retrofit that REGEDIT to Win98se). Within those CLASSES are the big three: CLSID 4,741,981, Interface 1,830,654, and TypeLib 568,080. Other large areas are in the easily flushable ActiveX Cache and Explorer UserAssist sections. FWIW, being my main development system it has the proverbial kitchen sink installed: every compiler and IDE I use plus too many support apps to count. This is how the registry really grows, needless COM bloat from software that insists on self-registering every possible object and library some executeable might need. Thankfully the good stuff I use day to day is pretty light on registry bloat (Opera, IrfanView, UltraEdit, GOMp, WinRar, PFE, most Games, Hacking Utilities, References). But stuff like Corel, Office, some Cameras, SoundForge, Adobe, InstallShield, Screenshot apps, (ad nauseum) still blindly follow Microsoft's insane duhfault habit of exploding the registry. As I have pointed out elsewhere, there are some things that can be done to shrink the registry footprint. Case in point, I was recently able to remove a pile of screenshot apps (SnagIt, FliSoft, HyperSnap, InBit, a few more) which used a couple of needless MB and just use the perfectly adequate (and free) MwSnap and IrfanView. I removed the .NET Framework(s) as well (big loss). I yanked Real Player and all its illegally long keys and values. Another massive example (but not for the faint of heart) I removed all the MSI sections, all of them. Some icon keys needed to be re-routed but I tested all the apps and NONE of them required the MSI hooks. Total savings was many MB of registry exports. If you install the PlatformSDK you will see just how much needless crap goes into that key structure, gigantic keys pointing to every dang .c and .h file in the package. Only Microsoft could have invented that MSI monster (hint: all of the data belongs in a private file!). But if you think this is something, those of you on WinXP right now export this key: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\TrayNotify] Pay particular attention to the value called: "PastIconsStream".

@WangoTango ... please describe all the steps exactly as you did them thus far in detail. Describe what you want to accomplish. More hardware details are needed (drives, mobos), software (OS before/after). I re-read your post a bunch of times and can not make heads or tails out of it. P.S. Nugent kicks arse!

Next day here, my previous post (the one just above this) was from yesterday. Today I did the same steps as described above, opened those three forums in three tabs from a saved Opera Session, and this time all three pages got hung up. I tried to F5 Reload them several times to no avail. They all looked like they were hanging up on the advertising banner. Closing the three tabs and pasting the URL's into three new tabs worked great, the three forums popped right up. Also note, there was no logged out problem, all three forums were logged in ok.

It has been happening on and off here as well. I have been using an Opera 'session' (kind of a list of webpages that you were looking at). This session has three tabs, with the root page of three MSFN Forums: Site & Forum Issues, Windows XP, and Windows 95/98/98SE/ME. When I load the session, the tabs get loaded with those three pages as I left them the previous day (still logged in naturally). I then press F5 Reload on each one to pull down the current page to each. Now on a 'bad' day, at this point I will then find that all three pages are logged off. So I then log in on one page, and then reload the other two and all is peachy. Strangely enough, today I saw something different, this may offer a clue of some kind ... After following the steps mentioned above (F5 all three tabs), I found that only the Windows XP forum was logged out. This one makes no sense to me (but perhaps it might to one of you Admins). I haven't looked at the cookies to see if they specify the forums individually or track Users globally, but the answer is in there somewhere. I figured it was worth mentioning. Hope it helps.

Hmmm, the Spell Checker seems to suck also. (Pssst, that is meant to be funny! )

Ditto here. Just started having to login a few days ago (apprx beginning of this month November 2008). Had this problem entire time using Opera 9.5x versions, don't remember ever logging in on the Opera 9.2x series. When moving up from Opera 9.5x to Opera 9.60 on October 16, 2008, the login problem suddenly went away. Thought it was gone for good. Two weeks later it is back daily. FWIW, I have noticed far less cookies accumulating in Opera 9.60 though. But ... since I see others here citing Firefox I guess Opera can be ruled out now. That Remember Me tick box is definitely checked. I even unchecked and checked it again. Over, and out.

@Multibooter, I remember about a year ago having to manually disable Winmgmt\WBEM on Win9x to allow an important app to work. It was conflicting with CPU-Z by Delattre, so you may want to keep an eye out for similar breakage. It may have since been corrected for all I know. Not to hijack the thread here, just a heads up.

I have a pretty good archive going of files like these. Here is what I see for this one: FILENAME SIZE DATE TIME VERSION SOURCE MSDMO.DLL ... 50,448 ... 10-24-02 ... 12:02p ... 4.90.2490.1 ...... *** (see below, scroll down) MSDMO.DLL ... 59,664 ... 06-08-00 .... 5:00p ... 4.90.3000.1 ...... WinMe MSDMO.DLL ... 11,264 ... 11-07-00 .... 3:16p ... 6.03.01.0400 ..... ? MSDMO.DLL ... 11,264 ... 10-30-01 .... 3:10a ... 6.03.01.0400 ..... Gspot221, WinDvd4011187 MSDMO.DLL ... 11,264 ... 08-17-01 ... 10:36p ... 6.04.2600.0 ...... WinXp(sp0)(sp1) [color="#008000"]MSDMO.DLL ... 12,800 ... 12-12-02 ... 12:14a ... 6.05.01.0900 ..... Dx90b (using)[/color] MSDMO.DLL ... 14,336 ... 08-04-04 ... 12:56a ... 6.05.2600.2180 ... WinXP(sp2) MSDMO.DLL ... 14,336 ... 04-14-08 .... 5:42a ... 6.05.2600.5512 ... WinXP(sp3) *** Many Sources! *** Wm7(01917) Wm7(01954) Wm7(01956) Wm7(3055) Wm8(5055) Wm8(5059) Wm9(2799) Wm9(2926) Wm9(2980) Gearpro605 Pradio21 WinFm11 Videocharge The green one is the one I have in use on Win9x systems. I have it sourced from Dx90b. As far as WMP, I believe all of my Win9x boxes have that hybrid WMP 10 courtesy of the MDGx site links. Please note however that when I do use multimedia on Win9x it is almost always in GOM Player which I find to be better in many respects. After doing a Karri FunctionCheck on each one I found that they are all identical with respect to enumerated exported functions and their ordinals. All eight files produce this exact same list: Ordinal ... Exported Function Name 1 ... dmoenum 2 ... dmogetname 3 ... dmogettypes 4 ... dmoguidtostra 5 ... dmoguidtostrw 6 ... dmoregister 7 ... dmostrtoguida 8 ... dmostrtoguidw 9 ... dmounregister 10 ... mocopymediatype 11 ... mocreatemediatype 12 ... modeletemediatype 13 ... moduplicatemediatype 14 ... mofreemediatype 15 ... moinitmediatype 15 functions listed. Presumably the functions themselves have been tweaked from version to version which would account for some of the differences seen in filesize. Not sure if this is useful, but looking at some of the other informational strings shows this (files in same order as above): VERSION PRODUCT CHARACTER SET 4.90.2490.1 ...... Microsoft® Windows® Millennium Operating System ... Unicode 4.90.3000.1 ...... Microsoft® Windows® Millennium Operating System ... Unicode 6.03.01.0400 ..... DirectShow ........................................ Windows - Multilingual (U.S. Standard) 6.03.01.0400 ..... DirectShow ........................................ Windows - Multilingual (U.S. Standard) 6.04.2600.0 ...... DirectShow ........................................ Windows - Multilingual (U.S. Standard) [color="#008000"]6.05.01.0900 ..... DirectShow ........................................ Windows - Multilingual (U.S. Standard)[/color] 6.05.2600.2180 ... DirectShow ........................................ Windows - Multilingual (U.S. Standard) 6.05.2600.5512 ... DirectShow ........................................ Windows - Multilingual (U.S. Standard) Hope this helps. Let us know what you discover.

Good idea. Folks should describe their quick fixes for things that get broken by a Service Pack update. It just might help someone out of a jam. I'll add a recent one: D-Link USB wireless receiver not working after WinXP SP3, no internet! I noticed that two D-Link command line utilities (AIRGCFG.EXE and WZCSLDR2.EXE) loading during startup with dependency errors. The utilities loaded user settings like SSID at each reboot, but were failing to do so now. The 'missing' dependency was from WLANAPI.DLL which was physically present in System32 where it belongs. D-Link however used an older version of that file which was since replaced by SP3. So I searched the entire HDD and found the squashed version stored in $NtServicePackUninstall$. I then copied this older file (aka 'localized' it) to the two folders under Program Files containg those two D-Link utilities. Rebooted, no errors. Just had to re-enter the SSID manually ... done. Lesson for developers, stop sticking files into System32 (and in Windows for that matter). It was a bad idea years ago and is even dumber now. Place a copy of system DLL's you depend upon into your private folder(s). Lesson for D-Link, after you total up the cost of all the support calls you are now receiving (and the corresponding negative publicity), find out which managers are responsible and send them the bill (or, just smack them around a little ).

Hi folks, Just asking a dumb question: On the FrontPage News, why do the UserNames of some people show up while others are missing? I looked for some setting on the profile page but could not find one. Specifically, on this thread, here is how the first three entries appear: #1 Posted by ( posts) at 21 Oct 2008 - 10:40 #1.1 Posted by MrCobra (347 posts) at 21 Oct 2008 - 13:16 #1.2 Posted by ( posts) at 25 Oct 2008 - 10:02 The first and third are mine. Just Wondering.

LOL, CharlotteTheHarl... that's all I see in the left column also. As protected as we are on Win9x with Opera/Firefox, we can still pick up a buttload of spyware/adware from running older program installers like those mentioned above. My best method of tracking changes involves snapshots made before/after doing anything risky. At the very least there must be a complete registry export and complete filelist. Doing this allows you to backstep manually to the previous condition. As I mentioned in that other thread, I have no experience with that Fast Explorer thing. And no-one else jumped in yet with personal experience. But the thing looks pretty dang cool to me. Please let us all know how it works out!