Jump to content

LoneCrusader

Moderator
  • Content Count

    1,441
  • Joined

  • Last visited

  • Days Won

    7
  • Donations

    $775.00 

LoneCrusader last won the day on September 13 2020

LoneCrusader had the most liked content!

Community Reputation

250 Excellent

4 Followers

About LoneCrusader

  • Rank
    Resistere pro causa resistentiam.

Contact Methods

  • Website URL
    http://

Profile Information

  • OS
    98SE

Recent Profile Visitors

8,269 profile views
  1. 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
  2. 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?
  3. 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
  4. 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
  5. 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.
  6. 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
  7. 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:
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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...)
  14. 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!)
  15. One year ago today... Rudy, you are sorely missed!
×
×
  • Create New...