Jump to content

PsycoUnc

Member
  • Posts

    258
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by PsycoUnc

  1. -ah, finally, a thread with my exact SiS usb 2.0 long-running headaches! :yes:

    -I'm having the exact same problem as this thread's creator: tried EVERYTHING, all mentioned in here and then some, several times each over the past 3 yrs that I've had this ANNOYING Matsonic 9327e+usb mobo (Sis 650GL, 7001/7002)... and the closest I get, is usb 2.0 APPEARING to be properly installed in device manager, but definitely no usb 2.0 speeds, same as poster... tried sooo many different drivers: all OS's drivers, all sis drivers, all orangeware drivers, all MS drivers, Maximus Decim, usbman, and one other that I believe Petr referred me to in a recent thread, to no avail... yet 2.0 works perfectly, with native MS drivers, in XP...

    The final result was: MDGx said, well, sometimes you're just screwed... lol... and I firmly (tho unfortunately) believe this... sigh :realmad:

    gl all, if ANYONE gets 7002 usb 2.0 ACTUAL SPEEDS in 98se, please let us know how!

    >;]

  2. -lol, yes, it makes sense, was just hoping it wasn't going to be this complicated to know exactly which updates to apply, how/when to apply them, etc. when using 98se2me... it's my fault, my general laziness, I should have been keeping a running log of all this stuff/updates/files, but hoped I wouldn't have to, hoped that such concerns would already have been taken care of by the uber-experienced pro's doing 98se2me+updates...

    -so, it does boil down to my original post: we have to do a file-by-file comparison of new updates, both for 98se and ME, to see which files apply to our 98se2me'd OS, and which ones don't, and then take a chance when it turns out that a 98se updated file needs to replace an old ME one... -Not extremely reassuring, considering I use 98se2me and MDGx's updates for stability reassurance, but now it's a bit more "iffy"... still a major plus, tho, don't get me wrong! Still VERY appreciative for everything MDGx, Gape, etc are doing! I'm just a little "OCD" when it comes to worrying about potential stability issues/unknowns... :blushing:

    {...and I'm far too FLAKY these days to keep track of everything in my head (too dam many meds, lol), + too lazy to chart it all down on paper/file; not a great combination B) }

    >;]

    (...was just hoping MDGx could tell us, during each new posted update, whether it's also appropriate for 98se2me'd OS's, instead of just "for ME" or "for 98se"... as he mentioned in his last post, he's pretty good by now at knowing right away which it is, would save us the time/effort/guesswork...)

  3. -bristols: -perfect! -thx for elaborating exactly my questions/concerns in a much clearer way. :yes:

    -and one thing more, MDGx: when we try to apply 98se updates containing files which should replace older ME files (from 98se2me), will there be a version conflict because all ME files (even old ones) contain higher version numbers than any new(er) updated 98se ones? Or will the newer 98se files (with lower version numbers) still be able to overwrite the current older (yet higher version #) ME files? And, if so, as Bristols also asked, will/could there be compatibility/funtion issues when only some of the ME files are (gradually) replaced by (updated) 98se files?

    [i also apologize if I'm missing some previously-stated simple answer(s)/reasoning(s) regarding these issues] :blushing:

  4. -hi MDGx, a little confusion here:

    I see you post many updates w/separate versions for either 98se or ME, and I was wondering: w/98se2me installed, how do we know which version of the update(s) to use? Do we have to manually compare the update files w/the files in our puters to see which ones were replaced by 98se2me, to know which version of the update(s) to use? In case I'm not clear: if an update contains a file that has been replaced by 98se2me, we should use the "ME" version of the update, not the 98se version, right?

    -Perhaps it would be best/very useful if you could specify for each update which one to use with 98se2me installed, since I'm sure you already know which versions to use, if 98se2me is installed... ?

    -Or do you update your 98se2me project every time an appropriate update is posted/released, thereby showing us whether or not we need to apply the specific update ourselves and which version to apply?

  5. -hmm, so we should also have usb 2.0 functionality if:

    1) sesp2

    2) max.dec.nusb2

    3) 98se2me, #2+#3

    ...

    -correct? I've tried it w/max.dec.nusb2 AFTER 98se2me, and it didn't work (plus no success w/OrangeWare drivers, either), but it should work in order listed above? I'll have to dig up a pre-98se2me backup and give it a shot... (I have SiS 650GL chipset, w/7001/7002 USB1+2; 2.0 works fine w/XP...)

  6. -a couple notes:

    IAA: -some older intel chipsets can NOT use the latest versions, and Intel (in some places) notes this; one of my puters has 815 chipset, and the latest IAA totally screwed everything... upon research, I found intel notes mentioning that certain chipsets must use older IAA...

    -Norton: (sigh... here we go again lol) Norton is Horrible for stability! How many times, how many people, how LONG must this be reiterated? Even if you don't have it "currently in memory", I've found, many times, just having it on the system AT ALL causes many unexplained headaches with win98se, and those unexplained headaches GO AWAY once it is (totally) removed!... just an experienced (and agonized) note...

    gl...

    >;]

  7. "thx for noticing"... lol...

    -thx for correcting that one mistake, but... that doesn't correct the overall 98se2me flaw... I hate to yell at ya, since you've done so much to help all of us, BUT... ya realllllly need to make sure this flaw doesn't happen w/other files, by making sure every (I know, this hurtz) file replaced by 98se2me first checks version numbers... if not, then we can't trust 98se2me in the future, which would be VERY unfortunate...

    -perhaps a loop call with a data file, would make it much easier than coding every single file call... -have u thought about doing 98se2me with other than just batch files? -perhaps a very simple virtBasic/etc prog?

  8. ?

    -does 98se2me option #1 or 2 overwrite NEWER versions of files, as well as the older ones?

    -I had newer xpsp2 version of CABINET.DLL, ran 1/9 98se2me #2 today, and it replaced it with older ME version... ???... that's not supposed to happen, is it? If yes, that's NOT good, would mean anytime we run an updated 98se2me, we have to also re-run all other "newer" tweaks/updates afterwards... ???

  9. -MDGx: re: 1/9 fix:

    "* Microsoft Windows 98/98 SE MSASN1.DLL build 5.00.2195.6824 Security Vulnerability Fix"

    -uh oh...

    -I already had a newer ver. of MSASN1.DLL (5.0.2195.6905), and that 1/9 fix of yours renamed it to msasn1.qfe, but it did NOT replace it with anything... I had NO msasn1.dll in windows/system anymore, and that broke winUpdate... (among other things, I'm sure)...

    ...as soon as I renamed it back, winUpdate worked again...

    ???

    [-EDIT: the specific winUpdate error was 0x80070485, supposedly relating to CABINET.DLL, and recommending to reinstall windows installer, but my cabinet.dll file was fine, and following the (annoying) MS instructions for "properly" reinstalling winInstaller of course didn't fix the error...]

  10. -tihiy: granted, it's not likely, but any possible security hole can/will eventually be exploited, and should be plugged... (of course, people on very old/slow rigs may be willing to take that chance, if it means better performance, so there will always be a use of and appreciation for your fix... not to mention, I'm still a bit "iffy" about using ANY program/fix from someone who's "anonymous"; my paranoia has kept me completely infection-free all these years... :yes: )

  11. -prophets: well, I was gonna call em win98se gods, but thought that was a little over the top... ;) And perhaps prophets was a bit overkill as well, tho not too far a stretch: they find stuff from newer ("the future") OS's/fixes and use em in old win98, as prophets would "find" info from future and use to improve things in the present... [ok, a stretch, but Prophets sounded nice at the time... of course, hadn't slept in 36 hrs, so was on fumes :P ]

    ...

    -winME/4526: -I see, was thinkin of win98se, not ME... sry... -guess I'm still blocking-out acceptance of the fact that some people prefer to use ME... (I'm still traumatized by tryin to use ME when it first came out :realmad: , so I kinda skip over any mention of using it now... ;) ) -I guess if ya yank out all the junk that made it so crappy/unstable, then it could be worthwhile... to each their own...

    >;]

×
×
  • Create New...