VOGONS


IDE to Compact Flash as MS-DOS boot drive.

Topic actions

Reply 60 of 69, by Ozzuneoj

User metadata
Rank l33t
Rank
l33t
goldeng wrote:

As @Jo22 has mentioned @Ozzuneoj, DOS is a read-only operating system and what I as well like very much about it. Unlike Windows that changes/updates files according to the hardware you're using. In my opinion there's a possibility that there are parameters in your 440BX BIOS that need to be changed in order to 'eat' the CF card and boot normally. You may also want to try to disassemble your CF adapter from the computer that it works on and to assemble it temporarily in your 440BX in order to verify whether the card is tied to a specific CF adapter model or not, which may cause it to not boot correctly on a different system that it wasn't installed on in advanced.

By the way, now that I think of it, you mentioned that you aren't able to boot from the CF card on a 440BX motherboard. Are you by any chance using the same motherboard (Intel SE440BX-2) that I'm having the same issue with?

I guess I wasn't real clear on what I'm doing.

I'm using an internal CF card reader front panel on my main system (i5 2500k, P67, Windows 10), and that's where I'm moving all the data around. The card worked in an old Gateway 2000 430TX+K6 233Mhz system using a basic CF->IDE adapter. When I move the whole cable+adapter+card over to my Wintec W6BXA 440BX system, it hangs at Verifying DMI Pool Data. I've tried changing all sorts of settings and nothing has fixed the problem. Any idea what specific BIOS settings might cause this? There are hardly any settings on the 430TX system (since it is an OEM board), and it just works. This 440BX board has a TON of settings though.

I did try doing a full disk copy from the Maxell 400x card I was using over to a Sandisk Ultra 333x card and it does the same thing on the 440BX system.

One thing I did discover in Windows 10 though, is that right clicking the removable drive in "This PC" and choosing Eject (or doing it through Disk Management) seems to actually let you reinsert another card in the removable drive almost immediately, where as using the "Safely Remove" taskbar icon seems to disable\remove the entire removable drive, which requires a system restart for it to read another card. This should make playing with CF cards MUCH easier.

EDIT: Also just tried using an 80-wire IDE cable, just in case that was an issue with the newer board (not likely since it is still very old) and it made no difference. Every one of the 80-wire cables I own has a blocked pin and of course this board HAS that pin, so I just poked a hole in the blocked cable end with a thumb tack. 😀 Tricky, but made no difference...

EDIT2: Of all the weird things... I've been playing with it more and when I change the type of drive for the CF card to "NORMAL" rather than LARGE or LBA, it gets stuck in the same place except it prints a lower case "j" on the line before hanging there. Strangely, I'm able to CRTL-ALT-DEL to reboot when it does this, where as I have to use the power button to shut the system down when its set to Large or LBA. Maybe I'm on to something... I just don't know what.

Now for some blitting from the back buffer.

Reply 61 of 69, by Ozzuneoj

User metadata
Rank l33t
Rank
l33t

Okay, I just tried booting plain DOS from my 440BX board using an old laptop hard drive and it does the SAME THING. So apparently this isn't a CF card or CF adapter issue.

Anyone ever experience a problem like this with a 440BX and plain DOS?

Now for some blitting from the back buffer.

Reply 62 of 69, by Jo22

User metadata
Rank l33t++
Rank
l33t++
EDIT2: Of all the weird things... I've been playing with it more and when I change the type of drive for the CF card to "NORMAL" […]
Show full quote

EDIT2: Of all the weird things... I've been playing with it more and when I change the type of drive for the CF card to "NORMAL"
rather than LARGE or LBA, it gets stuck in the same place except it prints a lower case "j" on the line before hanging there.
Strangely, I'm able to CRTL-ALT-DEL to reboot when it does this, where as I have to use the power button to shut the system down when
its set to Large or LBA. Maybe I'm on to something... I just don't know what.

Hi, I really don't mean to bother you, but did you clear the first 63 sectors of the card before (before installing DOS with another setting) ?
The drive geometry will be mixed-up, if you change these settings to something new after the card got formatted/partitioned with the old setting.
Not that this will cause any instant damage in terms of data loss, but a previously bootable copy of DOS would nolonger boot (until you change back).
CCleaner on Windows has an easy to use disk wipe feature, too (but wears off the card quite more). Or You could use the tool I mentioned. Or Linux.
- Things like FDISK /MBR, for example, won't necessarily fix or clear the Partition Table.

Legend: "NORMAL" is CHS (~500MB max), "LARGE" is E-CHS (~8GB max), "LBA" is ..well LBA. 😁

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 63 of 69, by Ozzuneoj

User metadata
Rank l33t
Rank
l33t
Jo22 wrote:
Hi, I really don't mean to bother you, but did you clear the first 63 sectors of the card before (before installing DOS with ano […]
Show full quote
EDIT2: Of all the weird things... I've been playing with it more and when I change the type of drive for the CF card to "NORMAL" […]
Show full quote

EDIT2: Of all the weird things... I've been playing with it more and when I change the type of drive for the CF card to "NORMAL"
rather than LARGE or LBA, it gets stuck in the same place except it prints a lower case "j" on the line before hanging there.
Strangely, I'm able to CRTL-ALT-DEL to reboot when it does this, where as I have to use the power button to shut the system down when
its set to Large or LBA. Maybe I'm on to something... I just don't know what.

Hi, I really don't mean to bother you, but did you clear the first 63 sectors of the card before (before installing DOS with another setting) ?
The drive geometry will be mixed-up, if you change these settings to something new after the card got formatted/partitioned with the old setting.
Not that this will cause any instant damage in terms of data loss, but a previously bootable copy of DOS would nolonger boot (until you change back).
CCleaner on Windows has an easy to use disk wipe feature, too (but wears off the card quite more). Or You could use the tool I mentioned. Or Linux.
- Things like FDISK /MBR, for example, won't necessarily fix or clear the Partition Table.

Legend: "NORMAL" is CHS (~500MB max), "LARGE" is E-CHS (~8GB max), "LBA" is ..well LBA. 😁

As mentioned earlier, this card had DOS put on it by cloning a VHD on a newer computer. It works on a 430TX but not on a 440BX. There were no settings like this involved in the setup process since it was done in Windows 10.

Now for some blitting from the back buffer.

Reply 64 of 69, by Jo22

User metadata
Rank l33t++
Rank
l33t++

As mentioned earlier, this card had DOS put on it by cloning a VHD on a newer computer. It works on a 430TX but not on a 440BX.
There were no settings like this involved in the setup process since it was done in Windows 10.

Ah, I see. Sorry then. Does that 440BX have got a CD-ROM drive, at least ?
It seems I'd be way easier if you did the partitioning/formatting on the actual hardware first.
Once this is done, you can throw the card into the CF reader on your Windows X machine and transfer files.
Both MS-DOS 6.22 and DOS 7.x (as part of Win9X) were once also available in CD-ROM flavors, I believe.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 65 of 69, by Ozzuneoj

User metadata
Rank l33t
Rank
l33t
Jo22 wrote:
Ah, I see. Sorry then. Does that 440BX have got a CD-ROM drive, at least ? It seems I'd be way easier if you did the partitionin […]
Show full quote

As mentioned earlier, this card had DOS put on it by cloning a VHD on a newer computer. It works on a 430TX but not on a 440BX.
There were no settings like this involved in the setup process since it was done in Windows 10.

Ah, I see. Sorry then. Does that 440BX have got a CD-ROM drive, at least ?
It seems I'd be way easier if you did the partitioning/formatting on the actual hardware first.
Once this is done, you can throw the card into the CF reader on your Windows X machine and transfer files.
Both MS-DOS 6.22 and DOS 7.x (as part of Win9X) were once also available in CD-ROM flavors, I believe.

Shouldn't really be necessary since it works on other boards. DOS's MBR and formatting aren't system specific are they? I can't imagine they would be.

Like I said, the reason I'm trying to do this is to have a portable DOS installation, so having to partition and install DOS on it wouldn't work for that use case. So far, I can't get this board to load DOS at all.

Now for some blitting from the back buffer.

Reply 66 of 69, by Ozzuneoj

User metadata
Rank l33t
Rank
l33t

Okay, I gave up.

I just downloaded Rufus and used it to install Freedos to my CF card and it booted instantaneously on the 440BX system on the first attempt. I'm running benchmarks and programs right now.

I tried for a couple hours to get MSDOS 6.22 onto a CF card but all of the tutorials that show up in Google searches are WRONG... none of the methods work, and none of the programs said to do this actually function properly. Unetbootin is useless for some reason. It doesn't show any drives other than my C: drive!? And all the different versions of Rufus refuse to use any ISO disk images I've tried to load (all downloaded from allbootdisks.com).

Anyway...

Hopefully Freedos is good enough for my needs as a portable DOS tester that doesn't care what system it is attached to.

I'm thinking this may be the next thing I'll try:
YT Tutorial - MS-DOS 7.1

I can install Windows 98... I've done that a million times and I own several licenses. I really really wish I'd seen this post before I spent all day messing with this. I only want MSDOS for compatibility... having the latest version with FAT32 support would be fantastic.

EDIT: I did the Windows 98SE converted to straight DOS 7.1 method in the thread above and it works perfectly on this 440BX system, using the same CF cards as before. I think I'll stick with this, as I'm much more familiar with the quirks and inner workings of MSDOS than Freedos.

Now for some blitting from the back buffer.

Reply 67 of 69, by Razor655

User metadata
Rank Newbie
Rank
Newbie

Looks line your card's firmware has removable bit set. If so, you can't boot MS-DOS natively from it.
But it is still possible to boot MSDOS with grub4dos using the 'map' feature. For exapmle you can map bootable floppy/hdd image from CF to ram and boot from it.
Personally, I dont like that grub4dos feature, so I'm think the better solution is to find CF with fixed media bit set. But nobody on ebay gives such information. 🙁 Only Industrial cards guaranteed to have fixed media bit set in their firmware, but they are too expensive and mostrly overkill. If you need something like 32GB or more, I think the best solution is to buy native ATA SSD - they are muuuuuh faster than almost any CF card and cost less than industrial cards with the same capacity.

- C&C: Red Alert Archive project
QDI Titanium IIB / P55C-200 / 64Mb RAM / 8Gb IDE CF / ATi 3D Rage Pro 8Mb / Sound Blaster CT2890 / 3D Blaster CT6670

Reply 68 of 69, by Jo22

User metadata
Rank l33t++
Rank
l33t++

Don't worry about that, DOS is too old to really care about that bit. 😉
Industrial cards are cool, though. Their access times and transfer speeds are usually quite good.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 69 of 69, by .legaCy

User metadata
Rank Oldbie
Rank
Oldbie

Well i have one cf installed as boot drive on my compaq lte 5300 and it works perfectly.
seek times are awesome and the transfer speed are the same, but that should be the limitation of the ide controller.
I'm currently testing sd to ide and they seems to work, my 486 had no problems with it.
about te size, well if your bios don't supports lba then ontrack disk overlay should work