• Content count

  • Joined

  • Last visited

Community Reputation

53 Excellent

About LoneCrusader

  • Rank
    Resistere pro causa resistentiam.

Contact Methods

  • Website URL

Profile Information

  • OS
  • Country

Recent Profile Visitors

1,551 profile views
  1. As far as I know you can't have "too large" a power supply, as the motherboard and devices will only draw as much as they need. The problems come when the devices draw more than the PSU can put out. I would trash the Celeron (known to gamers as CelerOWNED ) processor and replace it with the highest-clocked Pentium III that is compatible with that board. You will see a very significant increase in performance. Virtually any Pentium 4 (Socket 478/some Socket 775) motherboard is great for running Windows 9x as most of them have compatible drivers and some can use over 3GHz processors and 4GB of RAM (you'll need rloew's patch for that much RAM though). Boards newer than that can be used in some cases but require more effort and more non-free patches. See the sticky thread we have devoted to motherboards for more info (I know it's a lot to read and somewhat disorganized, but we hope it will be improved in the future). You've come to the right place for Windows 9x support. You won't find any haters here that will waste your time telling you it's old and to run something else.
  2. This card apparently uses the "memory banking system" that rloew and I discovered while experimenting with 512MB and larger nVidia cards. With rloew's NVSIZE patch you can make all 256MB of the cards memory usable under 98SE.
  3. It's normal behavior for Windows 9x as far as I know. Windows 95 doesn't use DriverVer entries either. I can't speak for Windows ME offhand but if I remember correctly I don't think it works there either. DriverVer entries first appear in Windows ME .INF's but this may simply be due to the fact that ME technically came out after 2K and shared some degree of driver interoperability.
  4. It may be possible to run 98 on this hardware, but in order to do so you will definitely need several patches from our good friend rloew and I almost guarantee you will need to install with "SETUP /P I" to disable ACPI. I have never tried to install 9x on hardware this "new," but it doesn't mean it's impossible. I have used 9x successfully on an X58 system and rloew has it working on a Z87 system. If you don't have at least rloew's RAM and SATA patches though, don't waste your time trying. This is hardly helpful. This is the dismissive attitude I see given to 9x users who want to use 9x on modern hardware on various other forums. I don't like seeing it here as well.
  5. The original incarnation of the UBCD apparently included the 98SE Setup files along with a MSBATCH.INF which provided a Product Key. This forced the project to be considered "warez" and a violation of copyright. MSFN cannot be the host of such a project or condone the posting of links to it as such. Now...This was all before my time here, and discussion of the issue since has been pretty much "taboo." I assume one could create a package that included everything from the original except these two problem items and it might be acceptable; but in the end it's not my decision.
  6. I'd like to register a vote against this, or at least to make the order switchable somehow. I had to track down a method of reversing it back to the old way on PaleMoon.
  7. Here's a link. Notes from MDGx on this fix:
  8. The next question is whether or not Windows 98/ME/2K can also use the updated CRYPT32.DLL (along with any interlocked dependencies it may have) from XP. Its possible it may just work, it's possible it may work with KEX or a similar approach, or it may not work at all.
  9. Never seen that before. Remove all of the floppy disk drives and controllers from the Device Manager and reboot, see if they all reappear. Does your system have a floppy drive? If not, you may need to disable the Floppy Disk Controller in the system BIOS. Beyond that I'm not sure.
  10. Windows 98 Second Edition and Windows ME do not need this patch as they don't suffer from the CPU clock speed bug to start with. Microsoft issued an official HotFix for Windows 98 First Edition (RTM), Q312108, which can be found here.
  11. Yes, you must keep the updated files installed by the FIX95CPU script. If older files from the original CD SETUP are allowed to overwrite them then it will undo the patch. Glad you got it working!
  12. So, did you use the latest FIX95CPU (v3) as instructed or are you using an older version? DUN14-95.EXE is still a recommended update but when using FIX95CPU as intended it should not be necessary to install it in order to get the system to boot. Boot into Safe Mode again and check the version of the NDIS.VXD file in the WINDOWS\SYSTEM folder (right click on it, choose Properties, then examine the Version tab) and report the results here. If it is not version 4.00.1113 then you need to re-run FIX95CPU per the instructions. You still didn't answer my other specific questions. It is important to know the specific details of the processor you're using since it is possible that there may be further bugs with CPUs clocked above 3.73 GHz as this is the highest clocked CPU I have to test with.
  13. As dencorso has already pointed out I will need a lot more information in order to even attempt to address your issue. What is the exact model and clock speed of the CPU? What motherboard are you running it on? How much RAM do you have (and if more than 512MB do you have rloew's RAM patch to fix it)? What steps did you take during installation? What exactly happens, and what error, if any, do you get? Those questions, at least, must be answered to begin with.
  14. Purely hypothetical, but it MIGHT be possible to use some updated files from XP to get secure sites working again under IE6. Even IE8 has issues with these sites unless one has either SP3 for XP x86 or installs specific HotFixes for XP x64 (as there was no SP3, only SP2). I mentioned this before in this thread (and this subsequently linked thread is also related), but I haven't had the chance to do any experimentation and I never use IE for anything anymore if I can help it. The KB articles for the HotFixes I used to fix my XP x64 problem may give an idea what files are necessary to make an attempt. I wonder whatever happened to maximus-decim and his "cumulative updates" for IE6? If he's still making these packages somewhere then he might be the one who could figure this out...
  15. You can't apply any of the patches until Windows has completed the first round of setup (unless you manually pre-patch all of the files on another machine and drop the resulting files into the \WIN98 SETUP folder in order to override the ones in the CABs). If you mean Step 3 in the post you made then you haven't run SETUP yet at that point. In order to use a 500GB SATA drive you will definitely need both the SATA and 48-Bit LBA patches in place. FDISK is known to be limited when calculating disk capacity. Usually it still works fine to partition a drive so long as you set the whole drive as a single partition or specify the partitions by the percentage of the drive to be used rather than by byte count. There are many other tools that can be used in place of FDISK if you wish, so long as you get a proper FAT32 partition created, formatted, and set "Active." I have no experience with SSD's so I can't advise you there. Note that in order to TRIM it under 9x you will need yet another solution form rloew.