VOGONS


First post, by DOS Retro

User metadata
Rank Newbie
Rank
Newbie

Hi people.

I have a little issues with my Hyundai SUPER-16TE PC

Floppy Drive A: 720KB? 3,5" - Ye Data YD-645C1545C at end of the cable (after twist)
Floppy Drive B: 360KB? 5,25" Panasonic JU-455-7 at the middle of the cable

I think the DS settings are correct, since it formats a 5,25" 360KB floppy correct with command: format b:
The issue is that if I insert a 3.5" 1.44MB in drive A, and placed some tape over the "720KB" hole, it still formats the disk also at 360KB

When i try the command:
format a: /f:720
it comes with "Parameters not compatible"

I think it's recognising the drive A: as a 5.25" 360KB drive.
Am i correct? How can i change this?

Reply 1 of 4, by rasz_pl

User metadata
Rank l33t
Rank
l33t

Bios needs to know what drives are installed. Bios sets up a special Diskette Parameters Table in Interrupt Vector Table (ram starting at 0) at offset 1Eh https://en.wikipedia.org/wiki/BIOS_interrupt_ … Interrupt_table that describes currently working FDD.

00000000 struct DPT // sizeof=0xB
00000000 { // XREF: seg000:FDD_par_Table/r
00000000 unsigned __int8 step_rate_head_unload;
00000001 unsigned __int8 head_load_non_dma;
00000002 unsigned __int8 motor_off_delay;
00000003 unsigned __int8 bytes_per_sector;
00000004 unsigned __int8 sectors_per_track;
00000005 unsigned __int8 gap_length;
00000006 unsigned __int8 data_length;
00000007 unsigned __int8 gap_length_format;
00000008 unsigned __int8 fill_byte;
00000009 unsigned __int8 head_settle_time;
0000000A unsigned __int8 motor_start_time;
0000000B };

IBM in its infinite wisdom didnt expect to support more than one type of floppy in 5150 BIOS and later was already too late for extend this in a clean compatible manner. Thus a hack was born where BIOS is constantly tracking which FDD is being accessed and switches this ram entry on the fly.
Sounds like your BIOS is not configured for two different floppies and doesnt know it needs to switch DPT.

Last edited by rasz_pl on 2026-04-19, 15:45. Edited 1 time in total.

https://github.com/raszpl/sigrok-disk FM/MFM/RLL decoder
https://github.com/raszpl/FIC-486-GAC-2-Cache-Module (AT&T Globalyst)
https://github.com/raszpl/386RC-16 ram board
https://github.com/raszpl/440BX Reference Design adapted to Kicad

Reply 2 of 4, by konc

User metadata
Rank l33t
Rank
l33t

I thought that the ROM of all the super-16 series supported 720K drives, but maybe that's not the case with TE. You can use DRIVPARM in your config.sys to tell dos what your drive is.

Reply 3 of 4, by DOS Retro

User metadata
Rank Newbie
Rank
Newbie
konc wrote on 2026-04-19, 15:45:

I thought that the ROM of all the super-16 series supported 720K drives, but maybe that's not the case with TE. You can use DRIVPARM in your config.sys to tell dos what your drive is.

Back in the days i never used commands like these in my computers. Also because they had 360KB drives, and after that PC it became a 486 where 1.44 was the standard. So i really never used 720KB/1.2MB drives.

I made a command DRIVPARM=/D:0 /F:2 /T:30 /S:9 and after a reboot MSD also showed a 720KB drive
After that, i did format a 1.44 floppy succesfull to 720KB (with the hole covered)

Thanks for the help.

Another question
Since the board had the bad leaking varta, it has been removed.
But what is the benefit of placing a new battery, since the drives are not stored in the BIOS? Even the MFM works without any issues.
If it is only for day/time saving, i better can leave it without battery?

Reply 4 of 4, by konc

User metadata
Rank l33t
Rank
l33t
DOS Retro wrote on 2026-04-19, 17:55:
Another question Since the board had the bad leaking varta, it has been removed. But what is the benefit of placing a new batte […]
Show full quote
konc wrote on 2026-04-19, 15:45:

I thought that the ROM of all the super-16 series supported 720K drives, but maybe that's not the case with TE. You can use DRIVPARM in your config.sys to tell dos what your drive is.

Another question
Since the board had the bad leaking varta, it has been removed.
But what is the benefit of placing a new battery, since the drives are not stored in the BIOS? Even the MFM works without any issues.
If it is only for day/time saving, i better can leave it without battery?

Great to hear it's working!

You are correct about the battery, its only purpose is to keep the RTC running. You don't need to replace it. When there is no setup utility it's very rare to have some error thrown and usually when the RTC is on a separate card.