Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


LoneCrusader last won the day on May 3 2019

LoneCrusader had the most liked content!

Community Reputation

215 Excellent


About LoneCrusader

  • Rank
    Resistere pro causa resistentiam.

Contact Methods

  • Website URL

Profile Information

  • OS
  • Country


  • Country Flag

Recent Profile Visitors

7,742 profile views
  1. I believe you may have assumed more from my reply than was intended. I have NOT used MULTCORE, nor do I have a copy unfortunately. It may or may not work with Windows 95; it is most likely untested in that environment unless Rudy made any tests in the past few years (most of his software was originally designed with only 98/ME in mind; only after I became closer to him and began helping test and debug things [and requesting 95 support specifically] did he spend much time on 95). Let me also clarify; any "application" you wish to use in this context would have to actually be compiled !WITH! the MULTCORE SDK. An application generically designed to use multiple processors, say on a later NT-based OS, will NOT use multiple processors under 9x without being REcompiled MULTCORE-aware. AFAIK, MULTCORE is a unique 9x-specific implementation, NOT a 9x-port of some existing NT capability. I've never had any issues whatsoever with HyperThreading. Never had to disable it to make 9x run either.
  2. Ah yes, have several of those. Loved the cases. I used to buy them just to get the cases and use them for building newer machines.
  3. Do you mean that you have NO USB ports at all from the beginning, or you DO have them BEFORE you install NUSB? AFAIK the X99 chipset boards do not have USB1 controllers, only USB2/USB3. This can lead to a situation where USBD.SYS is not copied to \WINDOWS\SYSTEM32\DRIVERS during installation. The USB2 drivers depend on it, but do not force it to be copied, expecting it to already be there because of the USB1 install routine. Try copying USBD.SYS to the correct location if it isn't there (but I think NUSB does that anyway... ) If the latest NUSB, using a WinME file, required another WinME file, don't you think it would have been included? Why would you install a VIA hardware-specific USB2 driver on a system that (as far as we know, and most likely, being Intel-chipset-based) does not have a VIA USB2 controller?
  4. It's been a long time since I worked with ATI cards and Windows 95, other than some experiments with an XP-era laptop (Mobility Radeon) which produced very weird results and I never solved the issues. As someone else pointed out above, I know for a fact that the Radeon 8500 does work fine under 95; I have the drivers CDROM that came with one and have used it. IIRC, the 9250 had a working package as well. Since the last 98 driver is of course still a VXD, then theoretically it should work under 95 as well, and thus theoretically all the same cards working under 98 should work under 95. There may be other incompatibilities or dependencies though. The Control Panels/SysTray shortcuts and such will definitely not work under 95.
  5. As others pointed out, I don't think Windows 9x can use WDM graphics drivers. I read somewhere years ago that video drivers must be VXD, but I no longer remember the source. We were able to load the HD Audio BUS driver (HDAUDBUS.SYS) that enumerates the actual HDA audio output device, but none of the actual HDA device drivers (Microsoft/Realtek/Sigmatel tested) would load, despite the fact that all required WDM functions were satisfied. Either the system would boot to the desktop and no sound was produced (MS driver on originally supported hardware), or the system would die in BSOD's and never reach the desktop (Realtek,Sigmatel). We were unable to debug these crashes. Work was also done on loading USB3 drivers under 9x. No success here either; Rudy commented that these crashes appeared to be the result of "Initialization has already failed and the Driver is cleaning up." From my understanding of MULTCORE, any program you wish to use it with must be compiled with "awareness" of MULTCORE in order for it to actually use multiple cores. (i.e.; You can't just install MULTCORE to your machine and expect any program(s) to simply automatically USE multiple cores. You must have the sources for, and be able to recompile, any programs you wish to use it.)
  6. Officially compatible/supported - no. However Windows 95 (OSR2.5 + FIX95CPU + XUSBSUPP) seems to run just fine on various Socket 775 boards. Your issue will be a lack of drivers for USB2 controllers, integrated HD Audio, and possibly integrated LAN depending on the chipset used. If you're prepared to use add-in cards instead of onboard, then you may bypass most of these issues. The unofficial NVidia drivers do work on 95, minus the control panels and such. These can be used with early PCI-E video cards, although extensive testing has not been done on the stability of such a setup.
  7. Funny you should mention this, it reminded me that Rudy once mentioned that I had made some DOS-scripted thing I was working on (FIX95CPU maybe..?) written less readable by changing the default color from Red to Blue.. After reading your post and looking at the page for a while, I wasn't really happy with the blue (or dark purple visited links) myself. ...So, the "readability" fix is in. Just for you, jaclaz. Had to dig deep back (20 years! ) into my old Starfleet Academy "Romulan" days to find a more suitable shade of blue that we used back then on our page. Not a fan of amber myself, but it may show up somewhere later, simply for the fact that it is viewer-friendly.
  8. A heads up for those who are interested; I have uploaded a few more pieces of Rudy's work to my site. These are mostly things that weren't advertised or well known.
  9. Intel-branded motherboards later than the D875PBZ are garbage for Windows 9x. The proprietary Intel BIOS is useless for configuring anything of importance, and many things are not configured in a 9x-friendly way, leading to various odd incompatibilities and errors. Third-party boards based on Intel chipsets are usually fine, especially if they use AWARD BIOS. Several years ago rloew and I spent many hours experimenting with some Intel boards similar to this one.. in fact one was a D945GCCR. Also included a D945GTP, a DP43TF, DP45SG, and a couple of others I can't remember offhand. All of these exhibited some strange issues under 9x; resource conflicts, problems using video cards, hangs when loading USB2 drivers, etc etc. Third-party boards (Gigabyte/MSI/etc) using AWARD BIOS based on these same chipsets did not exhibit these problems.
  10. I received one of these as well. I assume a spammer created an account and used the PM system to send out solicitations. This does not mean that the spammer actually knows your email address, he just abused the PM system. When I logged in the offending message had already been wiped out, so nothing to worry about. Hopefully someone higher up will give us a word on what happened, it's above my pay grade...
  11. Very convenient to omit the option to leave things as is, so long as it pushes the "rebranding" agenda, no? Yes, I've stated my opinion clearly. And it was not my intention to restart the debate; I simply pointed out the fault in the choices. But, since you apparently have decided to make a "snide" comment about it, complete with innuendo regarding the "thoughts/intent/motivation" of those who might oppose the viewpoint you're pushing it should be pointed out that we also have our share of those who have loudly, and clearly, and repeatedly "browbeaten" (to borrow a very good term that was used before) roytam1 toward taking this action, despite the fact that he does not see it as a problem. Also, to clarify another point, roytam1 also indicated that branding was needed to go along with any name change. So there are two criteria at work here; not just a name that he approves of, but also corresponding branding he approves of to go along with it. Anyone can spout off names, but there are very few, if any, of us who can produce "branding" of a quality high enough to correspond with the product. Now, I certainly have better things to do with my time, and no desire to spend any of it on this issue again. I've said what needs to be said up to this point. But do not behave as if any who oppose your viewpoint on the issue do not have the right to voice that opinion and/or point out the fact that this "election" is rigged. The one consolation is that, in the end, roytam1 makes the decisions.
  12. This is subjective, depending on which side of the "great debate" you come down on. Those who are advocating for (or going along with those who wish to) changing the name have created the poll(s), and as such have purposely omitted the option to leave things as-is.
  • Create New...