Image Map Image Map
Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Write problems with an SD card IDE hard disk emulaator and Windows 98

  1. #11
    Join Date
    Mar 2009
    Dublin, CA USA
    Blog Entries


    Quote Originally Posted by Chuck(G) View Post
    Other than the connectors, what's the difference?
    The price? I mean, they are "industrial"

    IBM 5160 - 360k, 1.44Mb Floppies, NEC V20, 8087-3, 45MB MFM Hard Drive, Vega 7 Graphics, IBM 5154 Monitor running MS-DOS 5.00
    IBM PCJr Model 48360 640kb RAM, NEC V20,, jrIDE Side Cart, 360kb Floppy drives running MS-DOS 5.00
    Evergreen Am5x86-133 64Mb Ram, 8gb HDD, SB16 in a modified ATX case running IBM PC-DOS 7.10

  2. #12
    Join Date
    Jan 2007
    Pacific Northwest, USA
    Blog Entries


    Well, yes, that. But if they were SLC rather than TLC or even MLC, I'd say that the price was warranted.

  3. #13
    Join Date
    Sep 2008
    SE MI
    Blog Entries


    Quote Originally Posted by sbx View Post
    I have a Pentium 166 MHz machine, which works fine with the original IDE disk from 96', but when I run Windows 98 from the SD card IDE hard disk emulator module, I get blue screen write errors and other page faults after the first boot and for example when I try to copy files, install Office etc.... The installation of Windows 98 completes without errors.

    I tried using 16GB and 4GB cards, but it made no difference. I use DOS 6.21 to partition the drive to 2GB Fat16. I have also tried using WHATIDE.EXE software to manually set the cylinders in BIOS, also without any luck...

    Do you think a CF card emulator would behave differently?
    A little late to the party on this one. I've been using CF's for quite a while and have been fairly successful on my 1000SX, 486/66, and on up the line. I've been very lucky with the relatively inexpensive 'SanDisk' brand and mainly use the 128 MB and 4 GB variety of CF's. But, these are becoming difficult to source these days. I've found that sometimes on a new CF, it helps if you first invoke 'FORMAT /MBR' prior to partitioning and formatting, as for what ever reason, sometimes the manufacturer has put or left something of a proprietary nature on the CF. Try that and see if makes a difference. Also, if your particular BIOS has the ability to 'find' the HD, give that a shot and accept what it returns for starters. Good luck.
    Surely not everyone was Kung-fu fighting

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts