Jump to content
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. ×


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Donations


Everything posted by LoneCrusader

  1. No, I can't claim that title. Or at least it was never given to me, lol. I suppose I can be considered as such for the 9x forum, but unfortunately I can't take on such a role for the older-NT family as well. I'm doing well to manage to keep up a daily check in on things.. RL issues are really taking a toll on all of my "computing" endeavors these days. - (And while I agree it may not be ideal to have so many "pinned" threads, I don't see the need to start changing things just for the sake of changing them. It's been that way for a long time and hasn't been an issue... Why the
  2. Sorry for the late reply, and I can't really offer much help... IMO, it's probably a hardware-specific issue with your system. But... By chance, when you encountered this issue with XUSBSUPP were you attempting to shut down with a USB drive still attached to the system? If so, this may be the culprit.. I rather doubt it in a way as I believe it would have been manifested somewhere before during all these years. But I do know that most, if not all, of the "power management" code was stripped from the RLUSB drivers (originating from Microsoft UMSS sample source for 98) as a first step towa
  3. Obviously, if you want to remove the entire pack, you should delete all files modified by it and replace them with the versions from the corresponding previous update(s). This pack was long ago superseded by XUSBSUPP; I see you are aware of it... What shut-down bug? I am not aware of any such bug, you seem to be the only one who has this issue?
  4. Updating which USB drivers, specifically? The only drivers directly associated with USB storage are USBSTOR.SYS and USBMPHLP.PDR. Neither of these has ever received an "update" of any kind from Microsoft for Windows ME. Both of these files are directly used, UNMODIFIED,* in NUSB for Windows 98. * = USBMPHLP.PDR requires a "downversion" patch to allow it to load under 98. This has no effect whatsoever on the rest of the code. As far as I know, you are the only person to ever make such a claim about this "32GB USB limit." If there were such a limit, it would have been widely reported
  5. I've never had any experience with this chipset, so I can't speak from any experience with it. Maybe the SATA adapter did in fact cause something to be "reported differently" to the BIOS which allowed a drive connected through it to boot where a similar larger drive directly connected would not. It's impossible to know. But I would definitely not place any faith in such an adapter "providing" 48-bit LBA support where the original BIOS does not. Only thorough testing with multiple writes + retrievals of data beyond the barrier can prove whether or not the issue is resolved, and even then the re
  6. Since you reminded me of this thread elsewhere, I realized I forgot to post this screenshot that I took back then for this purpose. There is no such limit.
  7. You may have booted with it, but did you actually verify that you were able to access and actually USE the entire disk beyond the ~137GB barrier, WITHOUT corruption or errors? There's a big difference in being able to boot with a newer, larger drive and actually being able to use it as intended/expected. AFAIK, there has never been an issue with "booting" from these larger drives on older systems, the problems only arise when you attempt to write data and/or access beyond the limit. It is my understanding that the adapters that are the subject of this thread only provide a translation of
  8. Despite the fact that it is deemed unnecessary in the main instructions, and that other members here report success without this step, I have always had to include it to get this working on systems that I have set up:
  9. Provided you 1) use rloew's PATCHATA to update ESDI_506.PDR on your Win98 installation (and your intended hardware does in fact support 48-bit LBA), or 2) keep your 98 partition limited to ~120GB at the beginning of the drive, then no, there is no problem using the 250GB drive. If the larger disk is connected via SATA, you will most likely also need rloew's SATA patch. re: 32GB limit; This is totally nonexistent. Windows XP (2K as well?) and later impose a false limitation and prevent you from creating a FAT32 partition larger than 32GB, but they manage larger FAT32 partitions created b
  10. Aside from the other issues in this post... PATCHMEM has absolutely nothing to do with ESDI_506.PDR, or SATA drives, or 48-bit LBA, or ATA in general, or anything remotely related to or resembling a hard drive whatsoever for that matter. A standard SATA to IDE/IDE to SATA adapter will most definitely not provide compatibility with 48-bit LBA drives on a system that does not already support this in the BIOS. Where does this stuff come from? -- Now, as to the original subject. These types of adapters are now very common and cheap.. however the quality can vary widely. Do yo
  11. Welcome to MSFN, Tony! I wish it were under better circumstances, but we're glad to see you here. Thank you for the picture of your dad.. I know I probably speak for several others here as well when I say I wish I had known more about Rudy and been able to get to know him better personally. I exchanged many, many emails with him, and always enjoyed hearing about whatever he was experimenting with at the time. We once discussed meeting up if I were ever in New York, but unfortunately I never got the opportunity... One never knows the future, but if I had had any idea he would be gone so soon I
  12. I understand where you're coming from with that, however I certainly don't believe it's too much to ask for them to keep their "unsolicited opinions" to themselves. I don't care if they "disapprove" or "dislike" what we're doing, I know they don't approve and I didn't ask them to agree with it. I only ask that they stop "disparaging" us with it. This is how "diplomacy" works. If they expect us to do something that they demand, then they can show good faith by ceasing their constant attacks. And, I hate to say it, but they have no right whatsoever to insinuate that someone is "stealing" co
  13. I'm not an expert on Open Source licensing either, but apparently someone here is going to have to become one... This whole business is ridiculous. I would prefer to see the great "dispute" settled as well, because it IS in everyone's best interests to NOT be fighting each other, BUT - NOT by simply giving in to the constant threats/intimidation coming down from "on high." I don't speak for anyone but myself, but if it were up to me I would not lift a finger to conform to any "demand" until some degree of mutual respect is established. The first step of which must include "them" putting a stop
  14. I've heard that this does indeed happen, but I don't have any experience with it. I'm a CRT monitor die-hard, lol. I have a few LCD monitors in my collection but I never use them. (Of course with a laptop you're stuck with it...)
  15. I assume this amount is for them to actively recover the data for you, not just for some recovery software? Is the price contingent upon them successfully recovering everything? Of course it also depends on just how "irreplaceable" the data is; or how hard it would be to "recreate" the lost items... If you have PayPal, some of us might be able to contribute a few dollars toward helping you... (for reference, if the conversion I'm getting is right this amounts to approximately $400 to $900 USD; seems a very wide price margin!)
  16. One year ago today... Rudy, you are sorely missed!
  17. I believe I read it on a website somewhere, not on a forum... I thought it was MDGx's site, but I think I was unable to find any such reference there whenever I last checked (but I no longer remember when that was, or how thorough my search was...); possibly it came from a site linked from his?? Interesting about VBEMP... I suppose experiments with .SYS video drivers might be in order if anyone has the time and hardware to experiment... a good first experiment might be to attempt to use a Win2K-compatible .SYS driver for a video card that we already know works under 9x with the proper 9x
  18. It's been a long time since I did any research into this, but previously I settled on the HP ZD8000 (or Compaq NX9600) for my own attempt at a high-end 9x laptop. It features a high-end P4 CPU, uses a desktop chipset so is capable of >2GB of RAM* (*3GB visible to OS with a BIOS mod; search for my name and "ZD8000" over at BIOS Mods), and has an ATI Mobility Radeon X600 graphics chip and AC'97 audio that can be made to work with available 9x drivers. These laptops have their quirks however, and it took me many failed attempts to achieve anything close to success. When I last worked on i
  19. Short answer; No. Despite the fact that some WDM (.SYS) drivers are supported under 9x, as far as I know, video drivers MUST be .VXD type drivers under 9x. I read that somewhere years ago, but I no longer remember the source. However; to be perfectly honest I don't know if it has ever been tried. We worked on HDAudio and USB3 drivers without any success, but never video. This is a very deep rabbit hole... I don't recommend such an experiment for most average users. For the record however, so that anyone else who ends up reading this will know: first (UNDER 9x, NOT NT!) run
  20. I've not had any direct experience with mobile nVidia cards... I bought a laptop some time ago that has one but I've not been able to find the time to do any experimenting with it; I had plans to try and use it with Windows 9x, but it has HD Audio, and rloew and I never managed to get HDAudio working under 9x. So, the only experience I have with mobile video cards and 9x comes from my HP ZD8000 (ATI Mobility Radeon X600) experiments. I do know that some 7xxx series desktop cards were supported by the last "official" 9x release, (81.98 I believe), but not (IIRC) the higher-end 78x
  21. Glad you got things running, (partially at least).. DLLHOOK is an API redirector; it's used to fool programs into thinking an API is present where the program expects it, when in reality it may exist in a different place or not exist at all under 9x. This can help you bypass missing exports/etc when programs are run. For Example; some programs expect a function in KERNEL32.DLL "IsDebuggerPresent"; this function does not exist under Windows 95. Using DLLHOOK, you can redirect this call to a different call (in a different DLL if necessary), thus circumventing the error, and allowing the pr
  22. There's always room for improvement. I don't like some of the decisions the PM team have made, but they're far ahead of the other "main" choices. Was just throwing out an opinion, since everyone else was doing so...lol
  23. Forget the system.ini tweaking game and install RLoew's RAM Limitation Patch. I would use the /M option with your setup. No more tweaking or jumping through hoops necessary.
  24. Chrome is trash. Firefox is now following said trash. Pale Moon is the last, best hope... (If only they weren't such an arrogant bunch...)
  25. Ah yes, as usual it's always someone else's fault when Tobin goes on a rampage. And I love how MC tries to make it sound like there's some kind of "opening" for everyone to work together.. - what a load of rubbish. Anyone but a fool or the willfully ignorant can see the way they have behaved toward anything they don't approve of or consider to be beneath them. With them it's more like "conform and obey, or die." Who would want to "work with" such an arrogant, self important bunch of jerks? Love this. Yes, a dislike button would be a nice wake up call for a lot of people in today's soc
  • Create New...