Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Compact Flash to IDE controller help

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Compact Flash to IDE controller help

    So I have picked up a CF to IDE controller card that uses a floppy power plug. I have a 2 GB CF card plugged in. It is formatted as FAT. I could get my 486 to recognize it as a slave drive, and the BIOS auto detect the correct size aand information for the card.

    I wasn't able to xcopy my C: drive to the flash card. It would give a write failure. I was able to use a Win 98 computer and plug the 486s HDD in as a slave to copy the contents over to the 98 PC. I was then able to recopy everything from the 98 PC to the CF Card. I plugged the CF adapter in as a single/master drive in the 486, and it sits there and does nothing. I've already changed the BIOS to recognize the CF drive as the only drive, but nothing happens.

    I do not have a copy of DOS 6 or Win 3.1, so I can't do a new install. Is there anyway to trick this CF card into believeing it had a clean install put on it?

    #2
    Many CF cards do not behave correctly as slaves. If you have two IDE channels, try putting the CF as a master on the second channel.

    Also, if there are jumpers on the adapter, how do you have them set?

    Comment


      #3
      My motherboard uses an expansion card for IDE, floppy, COM, Printer, etc. It only has one 40 pin IDE slot, but uses a master/slave IDE cable. I have the CF card plugged into the master location on the IDE cable. The jumpers on the CF adapter are set as: 1. Master, 2. +3.0 volts, and 3. 40 pin IDE (has 44 pin IDE for laptops as well).

      Comment


        #4
        I've seen the same behavior with my 486's. The BIOS will auto-detect the drive (as if it knows how big it should be), but then in DOS, calls to format the CF drive, or write to it, will fail when the drive is more than 504 MB.

        I do not have this issue on the affected 486 machines with CF cards that are 256 MB or less.
        I also do not have this issue with the same CF card on other older machines that do BIOS translation to get to capacities over 504 MB.

        You may want to check out XT-IDE Universal BIOS to act as a BIOS extension and allow your PC to use larger drive capacities. You'll either need a burned ROM of this BIOS and install it in a network card ROM-BIOS socket (if you have one). Alternatively, pearce_jj [look him up on here] has been working on a ROM card that just hosts BIOS extensions (and can be flashed with XT-IDE Universal BIOS).

        As a last resort, you might be able to use drive-overlay software to get around this limit. This would be loaded in your config.sys file (if you can get DOS to load from the CF card) or if you are intending to boot from another drive / device.

        Comment


          #5
          Do you have the ability to set up your IDE card to use PIO Mode 0? Some cards insist on using DMA which doesn't always work.

          Comment


            #6
            To be honest, I don't even know how to do that.

            Comment


              #7
              few questions -

              1. How did you copy the files? Did you make an image of the orginal drive and use that on the cf, or did you use xcopy etc...

              2. Do you know the exact drive settings? Have you verified them on a more modern pc? Use auto settings, then after rebooting go back in and write down the settings. Put those same settings into the bios of the pc u wish to use the cf on. Don't rely on the earlier machine to detect it correctly.

              3. Have you done an fdisk /mbr on the drive after formatting? First format with "/s" option, then fdisk with the "/mbr" option. Make sure to copy fdisk to the new drive first, and run it off that after formatting. It will save you from having to know the fixed disk number.

              4. Are you using a 40 or 80 wire ide cable?

              5. What format is it currently in, you say fat, but not what type, is it fat-16 or fat-32?

              6. What model / brand CF are you using? Is it a sandisk? If so you will need the dma tool.

              I use CF/ Microdrives in quite a few machines, and sometimes it can be a pain to get going but its worth the effort imho. If you need an image of a bootdisk send me a pm, ill whip one up with what you'll need on it. =)
              Last edited by twolazy; May 15, 2012, 01:15 AM.
              '. \ / .'
              '. .'``'. .'
              ......:::::::`.....`::
              Currently seeking a Compaq Deskpro 386

              Comment


                #8
                Sorry it took so long to reply, busy few days. To answer in order:

                1. I tried to xcopy on the 486 from C: to the cf card, but I would receive a "A serious disk error has occurred while writing to drive D:\. Press R to retry." And then it would sit there until I reset the computer. I had to manually remove the harddrive and place it in a Pentium II running Win98. I then had to drag and drop the entire HDD into a folder on the PIIs harddrive. Once I did that, I was able to swap the 486 HDD with the cf card and then xcopy the folder on the Win98 HDD onto my cf card. Upon installing the cf card back in the 486, the computer would sit idle and do nothing once past the memory test and BIOS screen.

                As a side note, I've been running this 486s harddrive without a jumper because it will not boot up if the jumper is in the Master position. And it wont start DOS in slave. It will only function properly in either cable select or no jumper at all.

                2. The cf card settings have been verified using a partition program on my Windows XP desktop. The BIOS settings for the original 486s drive are correct too, verified by the factory label on the drive itself.

                3. I've tried to type fdisk /mbr, but nothing happens and a new prompt appears. The /s option is not valid for my version of fdisk.

                4. This 486 uses 40 wire IDE. I have other 40 wire cables, as well as 80. Should I try putting 80 wire on the 486, or should I throw a 40 in the Pentium II and try initializing this cf card again on 40 wire?

                5. This cf card has been formatted (several times now, by me) in the FAT16 system. It has a maximum storage of 1900 or so Mbytes.

                6. This cf is a Transcend 2GB 133x card.

                Comment


                  #9
                  Whats the date of the BIOS? (should be on the bottom of the POST screen) I've seem some Phoenix BIOS allow funky CHS geometry to show a drive above 504MB, even in DOS. Despite that, it would fail to properly read/write to it without a BIOS card or drive overlay to provide it with real LBA translation. I have a 8GB Transcend x133 card and it works fine in a 486 with a SIIG I/O card with a translating BIOS chip.

                  Comment


                    #10
                    Your 486 IO board will almost certainly be using 5V signalling, so set the CF card to 5V. As said many don't work properly as slaves.

                    I'd suggest making a DOS system disk (format /s then copy fdisk and format onto it too) and also extract this utility onto it. Next remove the HDD, set the CF cards as master, and boot from the floppy. Run wipedisk to clear off the first 128 sectors of the CF card - hopefully this will work. Then reboot, again from the floppy, and use fdisk then format /s. After that with a bit of luck the system will boot from the CF card

                    Hope that helps.

                    Comment


                      #11
                      Originally posted by btrains View Post
                      As a side note, I've been running this 486s harddrive without a jumper because it will not boot up if the jumper is in the Master position. And it wont start DOS in slave. It will only function properly in either cable select or no jumper at all.

                      3. I've tried to type fdisk /mbr, but nothing happens and a new prompt appears. The /s option is not valid for my version of fdisk.
                      For many drives the Master jumper means exactly that -- you need to have a Slave attached. WD drives are an exception, however. What type of drive do you have?

                      The /s option that twolazy referred to was for the format command, not the fdisk command. It puts the system files on the disk so that it is bootable. Of course you need to have that partition already setup as Primary/Active in fdisk.
                      PM me if you're looking for 3½" or 5¼" floppy disks. EMail “ ” For everything else, Take Another Step

                      Comment


                        #12
                        My 486 is running with a Western Digital Caviar 1210.

                        Also, I wiped the partition on another computer, and reset the cf card as FAT16 with a 1900 MB size. I plugged it back into the 486, and ran "format d: /s" it was able to format the cf card but gave an insufficient memory warning and said it couldn't make an unformat disk. It then began to copy system files, but the "Attention: A serious disk error has occurred while writing to drive d:. Press r to retry" error came up.

                        I'm beginning to think I'm trying to do the impossible...

                        My BIOS are AMIBIOS from 11/11/92.
                        Last edited by btrains; May 16, 2012, 02:15 PM.

                        Comment


                          #13
                          Sorry, my bad. Even some of the WD older, smaller drives need to be unjumpered to run as stand-alone drives.
                          PM me if you're looking for 3½" or 5¼" floppy disks. EMail “ ” For everything else, Take Another Step

                          Comment


                            #14
                            Here's my latest attempt.

                            I took the WD drive out of the 486, jumpered it as master, and placed it as master in my Pentium II. I placed the cf card in slave mode at the slave position in this PII. I was able to boot into DOS. I did a format /s and it copied the files over. Then I placed fdisk on this card. I plugged the cf card back in to the 486 as master, and it proclaimed operating system not found. So I went back to the PII, and did an xcopy /s /e. The entire drive was copied to the cf card.

                            After the xcopy, I was able to boot into DOS on this PII using the cf card only. It wouldn't start Win 3.1 though. It gave a garbled error message and booted back to the prompt (I'm assuming driver errors, or too fast a computer for 3.1 to play nice).

                            I plugged the cf card back into the 486, and it gave me all types of hard drive errors. It said error reading disk 1, and said press f1 prob continue. Obviously it didn't load or anything since my 486 just can't read my cf card. Is the card too fast? I've jumpered my 486 down to 20 MHz to be compatible with some old software I am using.

                            Also, one of the things that runs in the autoexec.bat is a DOS version of Norton Disk Doctor. It has never found problems with my WD drive, but since I've been messing around with this cf card, the cf card will (when I can get it to boot as a slave, or master - on the PII) give an error message that there are partitions no longer working, and then gives the option to fix them. So I do that, and it claims to fix them and requires a restart. I restart the computer and then it runs Disk Doctor again, which, once again finds the same screwed up partitions that it just claimed to fix.

                            I've really screwed something up now!
                            Last edited by btrains; May 16, 2012, 03:18 PM.

                            Comment


                              #15
                              11/11/92 BIOS won't support a drive larger then 504MB. Unless something like EZ-Drive or Ontrack Disk Manager is installed, or you have one of those IDE LBA BIOS cards, the drive will NOT work properly in that 486.

                              Comment

                              Working...
                              X