Jump to content

LLXX

Banned
  • Posts

    3,353
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

Everything posted by LLXX

  1. See, this is why I never recommended using an automatic installer in the first place. There is just too much bloat and overhead associated with such (how hard is is to boot into DOS, copy a single file, and then reboot?), and if something goes wrong, whoever installed it in the first place now has no idea how to uninstall, because you need to have Windows functioning to use the (rather useless IMHO) "uninstall" feature. On the other hand, following my procedure, she would know to copy back the original file, and it is done in DOS which practically runs on every PC in existence. Also, this is why I recommend replacing your ESDI_506.PDR with the fixed exact same version, and also why I don't recommend using newer versions just because they claim certain benefits. Don't fix it if it ain't broken.
  2. What you need is an "import table editor". Kill that DLL completely from the import table. Of course, if/when it crashes it'll crash anyway... Then email them and tell them that their software must be of quite an awful quality if they aren't even confident enough to release a version that doesn't require added debugging sh­it.
  3. Indeed, recovering files from an NTFS drive is a bit more difficult due to the more complex structure of the file system.
  4. msvcr80.dll goes in the system directory (WINDOWS\SYSTEM32 on a default XP install) Stop using Norton. It's notoriously bad software.
  5. Take the keyboard out, turn it over, and hit the reverse side sharply several times. You'll be surprised how much crap accumulates under the keys. Maybe it was just a dirt particle or something wedged in the contacts.
  6. Hardware keylogger *in* the keyboard or inline in the keyboard cable. I doubt your victim is checking the hardware, but checking the software is quite simple.
  7. While in DOS, replace the existing ESDI_506.PDR with one of my fixed files, matching the same version. It's that easy.
  8. They changed the structure quite a bit between the 5.x and 6.x versions.
  9. I wouldn't worry about this. Open-source community is strong.
  10. 32Kb here, actually.I mostly store large (up to 4GBs) files, so it's not much waste for me. ...that's strange, since all OSs since DOS 3.2 (?) supported sector sizes other than 512 bytes ("Bytes Per Sector" field in superblock), and back in the days of MFM/RLL ST506/512 drives, sector sizes were anywhere from 512 to 8192 bytes.
  11. Are you sure that's a Home Edition key?
  12. Startup current for those hard drives are going to total quite a lot, especially for older drives with more "agressive" motors. This is also the reason why SCSI server drives normally have a switch to enable sequential spin-up. The newer drives have spinup currents (for the 12v rail) of approximately 2A, but some older ones may have much more than that (I have a 5.25" full-height unit that takes nearly 8A from the 12V rail to spin up)Also, don't forget about the 5v and the fact that the PSU rating is for all the voltages combined.
  13. Not one bit. I tried forcing the 900+ unified drivers for 2K/XP on 98SE, and it just BSOD'd.
  14. A 512 byte cluster size (1 sector) is supposedly usable on FAT32 for disks up to 2 terabytes, but for some reason XP doesn't like it. The delay after DIR is normal. It's probably the computation of the free space, as you've noted, or something similar.
  15. Это будет английским форумом. He's saying nLite doesn't work on the Russian version of Windows.
  16. LLXX

    MSFN School

    Hmm... this would be the "Illegal Win98 SE Good Reduce to order" http://www4.tranexp.com:2000/Translate/ind...hp?showforum=91 Noteworthy thread titles:
  17. Linux doesn't use the BIOS so I doubt it has the capacity restriction (it uses direct disk access). I would definitely upgrade that PSU so it will not be stressed as much; I recommend 400W.
  18. LLXX

    Windows Version

    With a hex editor, a boot disk that can access your drive, and a Brain.
  19. Yes, but where I am, they can't do anything about it
  20. LLXX

    MSFN School

    Translators are hilarious. http://www4.tranexp.com:2000/Translate/ind.../msfn.org/board Sample: :lol:
  21. I would definitely go with the proxy method, i.e. force all Internet traffic through the filtering proxy. Anything client-side is quite easily defeated if your users have the knowledge (and even filtering proxies can be, with even more knowledge... )
×
×
  • Create New...