submix8c

Sorry to bump this topic but... Does the Hotfix work for SP3 machines? I've downloaded both the v5 (sp2) and v6 (sp3). Have XP SP3 (wired) + Win 7 (USB wireless) on Westell Versalink 7500 which I believe I have set up properly on both machines; same symptoms. The reason for the bump is that it's not listed as "resolved". Guess I could just try it.

No other recourse due to licensing issues but to download the WAIK. Use a download manager to speed it up. I use FlashGet. The direct link can be found at the "Thank you for downloading..." screen under "If download does not start...".

Then you won't gain anything trying to go from win-98fe to 98se. You'd gain more by increasing the ram on the system.Agreed. And FWIW, I don't think an "upgrade" will wipe the Plus!98. Not for sure (I'd have to dig into my "stash"), but there may be a couple of items that may be "upgraded", but otherwise...

I think that's what I was trying to say.

Durn! Probably didn't even get the latest/lastest one...

1 - Define a User/Password in XP 2 - Share a folder in XP 3 - Set Local or NAT Connection in VPC 4 - Start 98 in VPC - NIC added automatically 5 - Create same User/Password 6 - Reboot, Sign into it and Set MS Network - reboot/sign in again

May I point out that any given ISO burning software will only successfully burn at the media's rated speeds? If it states "multispeed up to n-X" the "n" is not a "cover-all" and may or may not work. I use DVDInfo (other freeware probably available) which detects rated speeds and don't even bother attempting to burn at any other speeds. Just an FYI...

Version info Version 8.1b More on 8.2 and a link to it Both modules in question are included. Not really sure how you installed an XP-SP2 version and neither here no there. Just providing links to what you are looking for. You might be able to just install the above over the "erroneous" (unsure} as they all state that there is "no uninstall". edits - The DX9c should have worked on 9x/me if it was for 9x/ME. Also note the first link gives the MS links for the correct versions at the bottom. It appears that the version for the DX8 module given in your post is incorrect. Get the last correct version for 9x/me from the link(s) (the Dec2006 Redist). Also, can I safely assume that you run 98SE? You never did say (also seen post in the Flash for 95 topic).

Sprechen Sie Englisch, bitte. http://www.msfn.org/board/topic/18408-forum-rules-updated-must-read/ 2.d Be mindful of other users on this forum and post in English. If you must post in your native tongue, please include an English translation... Deutsch-Englische Übersetzung http://babelfish.yahoo.com/

Here goes - === Whether genius or dullard When momma's in sight Keep your trap shut You know she is right. === Happy Mother's Day!

Have you tried making a BAT/CMD that STARTS the hta and point AUTORUN to it? This is the way the UBCD98SE did it (no more info on that can be found here any more).

If you "show hidden files" the INI will show (look in the Desktop folder, as well as others e.g. the Music, Picture, etc under any given User Profile). Don't delete them, just be aware that the setting allows them to "show". Each defined Partition will have its own Recycle Bin folder in the Root.

Just worthy of note - a COM port is Serial so you will only have 1-way (either way) communication available at any given time, otherwise you'll have what's called "collision".

Poke around in the Registry at HKLM\ENUM\PCI for some info on what Windows "found". Beneath each will be the VEN_something and beneath that you will find the "culprits" (i.e. the "unknown" and the Modem). After that, google on the associated VEN_something. Has helped me find "unknowns" before.

MS Ver 2225 fix 32gb Scandisk problem (click it for info) UDMA-mode is not necessarily "directly" related to 48-bitLBA. It's the BIOS-aware ability to utilize 48-bitLBA (built into the HDD). Usually, backwards compatibility (UDMA-n) is also integral. The MS-fix (link above) is a "patch" for up-to 132gb as long as the BIOS supports it. The modules in the first post "patch" the MS "patch" to allow for 48-bitLBA, which exceeds the MS specification as long as the BIOS supports it. HTH (am I correct, all?) (p.s. I use this "patched" version as I have a 250gb-48bit HDD on a 48bit-aware PC) edit - since it's a very new HDD, it probably is 48-bit; BIOS must support it... edit2 - and the BHDD31 is a complete package... (re-read the link dencorso provided)

Not sure about the NT-side, but for cross-connection accesses with any other (e.g. XP, so probably the same rqmt), you must have User-A/Pswd-A and User-B/Pswd-B defined on both PC-A and PC-B, then sign on to PC-A with User-A and PC-B with User-B. HTH

MS is aware of the "problem". Many places to get it from.

Good results! Should be put in MDGx "Stickified" so it gets "stuck"... edit - lest I forget - Congrats and Way to Go, guys!

Tips here. They will still apply to your request for info (i.e. 9x is DOS-based). There are limitations to DOS partition location (and size), depending on the version of DOS involved, in that it can't be installed above a certain MB-limit. Multiple methods can be used (e.g. Install DOS then XP, Grub4DOS, DOS in a VirtualPC, etc). Bear in mind you probably won't be able to circumvent the limitations. Do a search (see SEARCH selection above) on "multiboot dos xp" and ignore anything related to USB, etc. You can get a lot from just searching "multiboot". edit - and there's a number of threads related to "how-to's" for recovery partitions here. Just search around a little in the appropriate sub-forum. An example search would be "ghost recovery" or "recovery partition"; same methods would apply (depending on you chosen "image"). It's all here on MSFN - you have to look for it...

??? FWIW, you may be able to contact MS and get a replacement (with legit key) by reporting the "fake" one. However, you will probably have to pay "something" for the replacement. Also, check the CD and the MS "how to tell" page (holograms and all). Was it in an unopened package (also, check the CoA against MS "how-to-tell")?

Just a comment - the tips given should definitely work, however... If it was "stolen", a savvy person would just remove the "bombs" from CD and re-burn. Your only option (as I see it, anyway) is to (as jaclaz said) keep it safe and not insert the key in the installation (make it ask you) in case it was stolen.

Interestingly, if you use a VBS it will do the job. Even using the MAC output of the VBS, you'll still have to modify it to do get a Batch to do it (or just do it in the VBS). Sounds like you now have to use a RunOnce BAT to execute the VBS to do what you want and you are now into learning VBS File I/O instructions (as well as a comparison routine). There are a number of folks here that can point you in the right direction (not me tho). One (or more) will be around soon enough...

@krelian - just a comment/explanation of the USB Mouse (AFAIK)... Depends on the BIOS of the MoBo whether it will work or not. In your case not, in mine yes. If I understand my BIOS, it has "enable USB Legacy Support" which allows for the BIOS "emulating" PS2 until the OS takes over at which point the Drivers are loaded for USB devices. In Safe Mode, no Drivers are loaded but the BIOS allows for the OS to "see" PS2 devices. Very nice. In your case, it appears you get one or the other (many older Compaq's/Gateway's are like that). So, your method of "switching" works. Use USB when not going to Safe (faster than PS2) and just "switch" when Safe is needed.

As johnhc correctly states, the PID info within SETUPP.INI (the ROOT of the CD) is important. If you are using a Retail Key (you stated so) then there are certain files you may need (in addition to the correct PID info) depending on the "borrowed" CD. Dell was notorious for "altering" the CD in such a fashion as to not even have usable OEMBIOS.xxx files (in the I386 folder) as they intended that you (generally) use CD#1 to boot from, then "copy" files from it and then the "supposed Full XP CD" (lacking needed files). It is possible to construct a Retail CD from it, however. I believe (in light of several other topics in reference to these "special files") that assistant can be provided. 1 - Open up the SETUPP.INI and list the contents (4 lines) 2 - Provide a list of the ROOT of the CD 3 - Provide the type of PC that the CD was initially used for ("borrowed" from) 4 - Can you provide the initial Service Pack Level of both your COA sticker and the "friend's" COA sticker (there are some minor variations in the I386 "special files" depending on this). The COA's should indicate this. After that, it may be possible to create a "true Retail" from files directly from MS.