• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Gape

98 SE SP 3.32

2,361 posts in this topic

Nice update. How soon before the final? Sorry I wasn't able to give more help with your error problem.

0

Share this post


Link to post
Share on other sites

I have fixed the MDAC 2.8SP1 bug. The final version is almost ready.

All I have to do is clean up the mdac inf file then add it to the SP. I'm going to need some testers before I release it.

I'm asking that all the testers, please test on a clean install. I can have the package ready sometime this evening.

Either PM me or post in the forum for the exclusive link. Thank you everybody..

0

Share this post


Link to post
Share on other sites

Well after my last post I thought more about what egrabrych posted about 7 messages back ... that I think, was the problem I had when my USB stuff didn't seem to work. I remember now that I did do some research and further testing with the USB problem and discovered that it was the Usbstor.sys file (v5.00.2195.6773) in the U98SESP3.EXE that "seemed" to be the problem ... I had used WinRAR to take all the USB items out of U98SESP3.EXE to check the versions with the USB versions in NUSB v3.5. I guess I just figured it would be faster to just put the Ghost backup back on instead of trying to delete and add USB items from NUSB 3.5. I am pretty sure I isolated the Usbstor.sys file (v5.00.2195.6773) as the "possible" problem but there may have been another file also ... but as egrabrych posted ... when I went to NUSB 3.5 and Usbstor.sys (v4.90.3000.1) ... everything seemed to work just fine.

On my Ghost backup which was from Oct 2011 at the time of the problem, I had NUSB 3.3 installed then after the USB problem with U98SESP3.EXE a few months ago (Jan) I decided to install NUSB 3.5 and now have a more recent Ghost backup with NUSB 3.5 installed.

So after reading egrabrych's post from yesterday, things started to refresh in my mind about Usbstor.sys being the culprit ... at least on my computer.

Hope this helps some ... but it doesn't seem to be a problem with most people when they install U98SESP3.EXE since there hasn't been any mention of USB install problems from anyone. Perhaps installing the U98SESP3.EXE package on a fresh Windows 98SE install works better than installing U98SESP3.EXE over an already installed Windows 98SE ... I have no idea about this, just a thought.

...

_____________

PROBLEMCHYLD,

Did you also fix the (potential) problem with usbstor.sys?

(see Duffy's post above)

____________________________

Edited by Fredledingue
0

Share this post


Link to post
Share on other sites

With all due respect for everyone involved, USBSTOR.SYS (v5.00.2195.6773) *requires* WDMSTUB.SYS for working. So, it's necessary to delete *all installed USB devices* from program manager, and insert them again one by one for redetection (as is stated just about everywhere in big capitals). When one fails to do so, the installation reamains as it was before the uSP, so WDMSTUB is not loaded and USBSTOR refuses to work. So, then, there's nothing for PROBLEMCHYLD to fix, because the issue is a PEBCAK! :whistle:

USB 2.0 NOTICE - Unplug all USB devices. Install main updates.

Remove all current USB/EHCI drivers + controllers from Device Manager in safe mode. REBOOT!

Let all drivers redetect on startup. Plug in USB devices one at a time.

0

Share this post


Link to post
Share on other sites

I assume "the insert USB devices one at a time" rule only applies to the first time? Once all the devices have been correctly identified, then you can leave everything plugged in for subsequent reboots ?

Cheers and Regards

0

Share this post


Link to post
Share on other sites

Sure.

0

Share this post


Link to post
Share on other sites

With all due respect for everyone involved, USBSTOR.SYS (v5.00.2195.6773) *requires* WDMSTUB.SYS for working. So, it's necessary to delete *all installed USB devices* from program manager, and insert them again one by one for redetection (as is stated just about everywhere in big capitals). When one fails to do so, the installation reamains as it was before the uSP, so WDMSTUB is not loaded and USBSTOR refuses to work. So, then, there's nothing for PROBLEMCHYLD to fix, because the issue is a PEBCAK! :whistle:

USB 2.0 NOTICE - Unplug all USB devices. Install main updates.

Remove all current USB/EHCI drivers + controllers from Device Manager in safe mode. REBOOT!

Let all drivers redetect on startup. Plug in USB devices one at a time.

I was reading that on the sp3 page notes. As only a semi-techie, my oldest machine with usb ports from 1998 (currently with 2.1a sp on it) shows a "Universal Serial Bus Controllers" area in Device manager with "Intel 82371SB PCI to USB Universal Host Controller" and also a line "USB Root Hub".

Do I delete all of those? Will I be looking for other entries too in Device Manager after the sp3 update? Entries that will be added during the sp3 update itself? Also, is there a reason that the first time removal has to be done only in safe mode?

Sorry if these sound like questions I should know.

Edited by billyb
0

Share this post


Link to post
Share on other sites

Also, is there a reason that the first time removal has to be done only in safe mode?

Sorry if these sound like questions I should know.

Yes, to make sure no drivers are loaded. Sometimes it just sooooooo muchhhhhhhhhh easier just

to follow the instructions. Thanks dencorso.

0

Share this post


Link to post
Share on other sites

Here's a detailed cleanup procedure, from USBMan.

Also read Safe Mode Device Manager (vs. Normal Mode), by DNA, from annoyances.org, quoted below for easy reference.

Safe Mode Device Manager (vs. Normal Mode)

Thursday, August 23, 2007 at 8:25 pm

Windows 98 Annoyances Discussion Forum

Posted by DNA (553 messages posted)

When installing the Generic USB Mass Storage Driver on an existing Win98SE install, I remove all USB devices from Device Manager in Safe Mode.

Safe Mode Device Manager shows devices that are NOT 'currently installed' (but are still logged in the system), unlike Normal Mode Device Manager.

For instance, in Normal Mode Device Manager, you will only see your currently installed optical drives in the CD-ROM tab, whereas in Safe Mode Device Manager, you will see every optical drive that has ever been installed in that computer (even all of the external optical drives that were ever used, as applicable), unless/until you remove them from Safe Mode Device Manager.

You might be surprised at how many conflicts can be resolved by the correct use of Safe Mode Device Manager. It is generally safe to remove any listing for an internal device that is known to be no longer installed in the system, and it's even a good idea (to prevent possible conflicts).

Removable USB devices don't show up in Normal Mode Device Manager unless they are plugged into the system, so you can't remove them from there unless they're plugged in, and removing them from (Normal Mode) Device Manager while they're plugged in may not be a good idea in certain cases!

In Win98 Safe Mode, USB is disabled, so you can safely remove any and all removable USB device listings from (Safe Mode) Device Manager.

So, before installing the Generic driver, you should uninstall all of the removable drives' Win98SE drivers in Normal Mode, then boot to Safe Mode and remove the drives' listings under Disk Drives and Universal Serial Bus Controllers, as applicable.

I've done this procedure for several 'existing' Win98SE installs (on my 1.1 Athlon, and others' computers), and the Generic driver has worked fine in every case...

0

Share this post


Link to post
Share on other sites

Basically, Apple tried to lock up your media files with proprietary databases on their iPods and force you to use iTunes

The following is probably OT, but since you brought it up...

Best critique of iTunes that I've seen, if a bit salty. His experience pretty much matches mine. One time my wife, a pretty smart cookie, bought an iPod and asked me to figure out how to use it since she couldn't. All she wanted to do was to download MP3s of talk shows. I tried it and felt like I was being railroaded into doing things one specific, convoluted way that didn't work very well in any case. We ended up getting an unpretentious (and much cheaper) Sansa Fuze where we can simply download whatever and drag-and-drop it into the player, no muss no fuss. Never looked back.

--JorgeA

0

Share this post


Link to post
Share on other sites

First of all, I appreciate the additional information on the USB matter, Device Manager and other things that have been posted. In my case, I have limited knowledge about certain things which includes USB and Device Manager ... I use them and can work with them but I'm always on the lookout for more information. Dencorso, I got some answers from the links that you posted ... I never saw anything anywhere over the years that Device Manager should be "cleaned out" at least once or every now and then. When I was in Device Manager - Safe Mode earlier ... I noticed that there were many more items to delete under Universal Serial Bus Controllers than there are in Device Manager - Normal Mode. I wondered about that but the one article sort of clears that up.

From article:

"Safe Mode Device Manager shows devices that are NOT 'currently installed' (but are still logged in the system), unlike Normal Mode Device Manager."

"Removable USB devices don't show up in Normal Mode Device Manager unless they are plugged into the system, so you can't remove them from there unless they're plugged in, and removing them from (Normal Mode) Device Manager while they're plugged in may not be a good idea in certain cases!"

.... so that definitely explains why USB items have to removed from Device Manager while in Safe Mode and not Normal Mode.

In my case I did follow PROBLEMCHYLD's instructions while working with these USB devices.

"USB 2.0 NOTICE - Unplug all USB devices. Install main updates. Remove all current USB/EHCI drivers + controllers from Device Manager in safe mode. REBOOT!

Let all drivers redetect on startup. Plug in USB devices one at a time."

... however, I knew nothing about WDMSTUB.SYS and how it is connected to USB items or USBSTOR.SYS in particular. I can't speak for others but all this "extra information" that you and others post are a big help to me in understanding the inner workings of my computer.

dencorso :

"With all due respect for everyone involved, USBSTOR.SYS (v5.00.2195.6773) *requires* WDMSTUB.SYS for working. So, it's necessary to delete *all installed USB devices* from program manager, and insert them again one by one for redetection (as is stated just about everywhere in big capitals). When one fails to do so, the installation reamains as it was before the uSP, so WDMSTUB is not loaded and USBSTOR refuses to work."

I went into Device Manager - Safe Mode last night and found many old items to remove. A good example was under the CDROM tab .... there must have been close to 10 or 12 items that I removed ... from older CDROMs that I no longer use ....

From article:

"For instance, in Normal Mode Device Manager, you will only see your currently installed optical drives in the CD-ROM tab, whereas in Safe Mode Device Manager, you will see every optical drive that has ever been installed in that computer (even all of the external optical drives that were ever used, as applicable), unless/until you remove them from Safe Mode Device Manager."

I have been fooling around with these USB drivers in the interest of seeing if I could possibly get a faster transfer speed between a flash drive and my computer. I dealt with this in another post in asking USB file transfer questions.

Anyway, all information and links appreciated.

...

Edited by duffy98
0

Share this post


Link to post
Share on other sites

Does this applies to *ALL* USB devices or only to mass storage USB devices?

I have a couple of items like a drawing tablet which are not used to store datas on it.

°°°°°°°°°°°°°°°°°

0

Share this post


Link to post
Share on other sites

I believe it means "ALL" USB devices.

Cheers and Regards

0

Share this post


Link to post
Share on other sites

Some years back, I had a problem with the original USB Drivers on my 98FE System. If I copied a large amount of data to a Flash Drive I would get a BSOD with a Disk Write Error Message, especially if I was browsing during the transfer. Whe I rebooted, there was significant corruption found on my Hard Drive. Typically an entire Sector of FAT data was filled with garbage and to make things worse, the corresponding backup FAT Sector was also destroyed. Sometimes a Directory Sector was also filled with garbage. This type of corruption could easily render a Partition useless, depending upon where the damage occurs. I managed to recover my data but only through massive manual hunting and patching. You cannot use SCANDISK as it makes things worse.

The problem appeared to be only in 98FE, so I posted some warnings about using 98FE with USB. Some time later I setup a system to do some more research into the issue but was unable to reproduce the problem.

I was reading that on the sp3 page notes. As only a semi-techie, my oldest machine with usb ports from 1998 (currently with 2.1a sp on it) shows a "Universal Serial Bus Controllers" area in Device manager with "Intel 82371SB PCI to USB Universal Host Controller" and also a line "USB Root Hub".

Careful not to "stress" the olde 82371SB, it will break. See : http://www.usbman.com/Guides/known_issues.htm

Joe.

0

Share this post


Link to post
Share on other sites

I assume "the insert USB devices one at a time" rule only applies to the first time? Once all the devices have been correctly identified, then you can leave everything plugged in for subsequent reboots ?

Cheers and Regards

Yes, it only needs to be done once :lol:

Does this applies to *ALL* USB devices or only to mass storage USB devices?

I have a couple of items like a drawing tablet which are not used to store datas on it.

°°°°°°°°°°°°°°°°°

Yes

I believe it means "ALL" USB devices.

Cheers and Regards

Yes, it means ALL
0

Share this post


Link to post
Share on other sites

Congratulations for the work you all do to keep life in Win98.

I take this opportunity to point out that the instalation of HP printer on the network K850dn stops with the declaration of the impossibility to load libraries Tpc Mib.

greetings

0

Share this post


Link to post
Share on other sites

Congratulations for the work you all do to keep life in Win98.

I take this opportunity to point out that the instalation of HP printer on the network K850dn stops with the declaration of the impossibility to load libraries Tpc Mib.

greetings

Are you using the right hp drivers? Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

Yes, the drivers are original hp,

specifically the version 2.1 service pack did not have this problem.

See http://support.microsoft.com/kb/261302

I thought about the possibility of incompatibility with the library Snmpapi.dl

Thank you for your attention

I don't know what to tell you. The service pack doesn't have anything files from 261302.

Therefore it can't be the service pack. I have a HP 1320 and don't have any problems. Good luck finding the solution.

I going to post it here since I'm already typing.

For anyone thats having problems and doesn't give details, a step-by-step description,I WILL IGNORE YOU! I WILL NOT ATTEMP TO EVEN TRY AND FIND A SOLUTION FOR YOU. TAKE THE BITTER WITH THE SWEET.

0

Share this post


Link to post
Share on other sites

(Semi-)Clean Install Report

Sorry for the long-ish post, but first off, i want to thank everyone, especially PROBLEMCHYLD, for all the work and input on this very-worthwhile project!

Anyway, hope i'm not "jumping the gun" (as uSP 3.0 is not yet final), but just out of curiosity... and because PROBLEMCHYLD recently asked it... and because of potential issues reported in recent posts, i did a (semi-) clean install of the Apr-01 uSP release. I used an old IBM+Intel PII+440BX/ZX laptop that i keep around mostly to test Win9x non-KernelEx software compatibility. (I do use KEx on my newer main system though.)

Here's how i proceeded:

1) Reformatted the harddisk.

2) Installed Win98SE (custom).

3) Installed Intel Chipset Software Installation Utility.

4) Installed video driver. (Couldn't stand to look at VGA 640x480x256 for too long!)

5) Installed IE6 SP1 (everything except OE and multilanguage).

6) Installed uSP "Main Updates" (without any of the options).

7) Installed all the uSP options except "IE Core Files" (both), "Performance Tweaks" (grayed out), and "Power Management Trouble Shooter" (grayed out).

Everything seemed to go smoothly -- no noticeable installation issues, and the hardware and Windows boot up fine -- though obviously i haven't done much with it. And unfortunately, i don't have the means to test most of the options after installation.

Note that this computer has USB 1.1 -- not USB 2.0. I don't know if that's significant in terms of testing uSP or the disk issues recently mentioned.

Anyway, i installed no manufacturer-provided USB device drivers, and my USB flash discs, Zip drive, portable harddisk, diskette drives, camera (which appears as a flash disc), and a multi-card reader (which appears as multiple "Generic Storage Device"s) all installed ok after plugging them in. (The other card reader was not so lucky -- identified as "eUSB SmartMedia Adapter" -- Windows couldn't find a suitable driver. And i did have to tell the system that the portable harddisk was "removable" via Device Manager > Disk Drives > Settings; otherwise, it acted quirky.)

Note that "Performance Tweaks" and "Power Management Trouble Shooter" options were grayed out -- "Performance Tweaks" probably because it has 96mb RAM (uSP 3.0 uses 128mb as the limit, whereas uSP 2.1a used 64mb), but i'm not sure why "Power Management Trouble Shooter" was grayed out.

I noticed that Windows Management Instrumentation took a long time to complete after rebooting (Windows 98 Setup: "Updating System Settings...") -- i was starting to worry that it hung, but it finished ok.

And a note of caution: Be extra aware that the "Windows 95 Shell Swap" option *significantly* alters the functionality of the interface... and a few of its changes are somewhat-annoying. I installed it rather absent-mindedly, and was surprised at the changes it wrought. BE CAREFUL NOT TO INSTALL THIS OPTION BY ACCIDENT! (Like by just clicking all the option boxes... like i did -- hah!)

So overall, i'm quite impressed with the ease of installation, up-to-date-ness, and increase in functionality that uSP provides. (Except for the "Win95 Shell Swap" option as previously mentioned -- watch out!) It makes re-installing Windows 98SE *so* much-less painful and tedious... and much-less "hit and miss". Kudos!

- Doug B.

0

Share this post


Link to post
Share on other sites

I get this error when I install MDAC 2.8SP1 with all options checked in the service pack.

The weird thing is, when you run the MDAC option by itself everything installs without errors

or when you install all options without MDAC you get no errors. Anyone know how to fix this?

0

Share this post


Link to post
Share on other sites

Note that "Performance Tweaks" and "Power Management Trouble Shooter" options were grayed out -- "Performance Tweaks" probably because it has 96mb RAM (uSP 3.0 uses 128mb as the limit, whereas uSP 2.1a used 64mb), but i'm not sure why "Power Management Trouble Shooter" was grayed out.

- Doug B.

It was a bug, thanks to you I was able to fix it instantly. People have to understand what I mean by testing. We are (NOT)

here to see if the files work, we are here to make sure they all install correctly along with the registry keys. We know the files work

because we have been using them for years. Thanks for testing. I will send you a sneak peak of the final build.

0

Share this post


Link to post
Share on other sites

Problemchyld,

Just like that: Try to set a "wait" time (or delay) in the installation script.

Maybe the computer needs a rest, or need to finish a task even if this task is reportedly finished.

In DOS you can run wait.exe, a small executable which does only that.

3 independant versions here:

http://www.createwindow.com/raewebsite/rae-watx.htm

or

'>http://www.petersen.de/content/contenido-4.6.4/cms/front_content.php?idart=163

or

'>http://dpotter.net/technical/2007/09/utility-to-wait-for-a-process-waitexe/

I suggest to set a 3 second delay between each update.

(you can't have fractions of a second unfortunately).

As MDGX used to say: HTH

0

Share this post


Link to post
Share on other sites

Thanks Fred, but it only happens on MDAC. I 've been reading online about mdac memory leak. I believe mdac

has to be installed by itself. I 'll try the links you gave and see what happens. Thanks again.

0

Share this post


Link to post
Share on other sites

I suggest adding a warning to the package or the page that says something like this :

"if you have previously installed autopatcher then DO NOT install uSP3, it will result in unbootable windows (including safe mode)"

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.