DTK 386SX Clone and Phoenix 386 clone.
DTK 386SX Clone and Phoenix 386 clone.
The DTK 386SX clone is pretty much completely working (apart from that nasty menu config bug - does not show up in config menu) and for the Phoenix 386 I am just looking for a newer BIOS (at least 1989, the 01/15/1988 version has non-working setup).
Patch files:
Patch files:
Last edited by nerd73 on Wed 19 Aug, 2015 10:14 pm, edited 1 time in total.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
Why does the 1/15/1988 version of the Phoenix 386 BIOS have a non-working CMOS setup?
Re: DTK 386SX Clone and Phoenix 386 clone.
Not sure, but it's the BIOS I had in the original zip. For some reason the keyboard does not work at all in setup. I may try a later version from 1989 or later to see if that works.ppgrainbow wrote:Why does the 1/15/1988 version of the Phoenix 386 BIOS have a non-working CMOS setup?
I'm gonna have a look at the source code to see if I can try to add the Award 386 (January 1994) clone.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
That sounds good! As far as I know, the 1/15/1988 version might have had a bad dump. But if you have the 1989 (or later version) of the generic Phoenix 386 BIOS, let me know.
Re: DTK 386SX Clone and Phoenix 386 clone.
Struggling to find one newer than 1988. Found a 286 bios dated 1989 but it seems to be for an entirely different chipset.ppgrainbow wrote:That sounds good! As far as I know, the 1/15/1988 version might have had a bad dump. But if you have the 1989 (or later version) of the generic Phoenix 386 BIOS, let me know.
Should I point out that the 1/15/1988 BIOS ROM I found was for an INTEL chipset? (Intel chipsets in the late 80s were turds but they got serious about it circa 1994)
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
The 1/15/1988 BIOS ROM that you found was for a Intel-only chipset. If it were to be implemented in the next revision of PCem, the ability to use other CPU types, AMD and Cyrix would have to be grayed out.nerd73 wrote:Struggling to find one newer than 1988. Found a 286 bios dated 1989 but it seems to be for an entirely different chipset.ppgrainbow wrote:That sounds good! As far as I know, the 1/15/1988 version might have had a bad dump. But if you have the 1989 (or later version) of the generic Phoenix 386 BIOS, let me know.
Should I point out that the 1/15/1988 BIOS ROM I found was for an INTEL chipset? (Intel chipsets in the late 80s were turds but they got serious about it circa 1994)
If you're lucky, you might find a old computer capable of using a 386SX/386DX processor with a generic Phoenix 80386 ROM BIOS from 1989 or 1990.
Re: DTK 386SX Clone and Phoenix 386 clone.
Back then, I believe chipsets did not affect CPU choice as much as now. (except for a few oddities, like the UMC Green only working properly with UMC chipsets) I am pretty sure the AMD and Intel 386 were identical, and software could not tell between them. Perhaps Cyrix, as that would prob. be incompatible though. But the issues arise even with an intel CPU, so there is some problem with the ROM.ppgrainbow wrote:The 1/15/1988 BIOS ROM that you found was for a Intel-only chipset. If it were to be implemented in the next revision of PCem, the ability to use other CPU types, AMD and Cyrix would have to be grayed out.nerd73 wrote:Struggling to find one newer than 1988. Found a 286 bios dated 1989 but it seems to be for an entirely different chipset.ppgrainbow wrote:That sounds good! As far as I know, the 1/15/1988 version might have had a bad dump. But if you have the 1989 (or later version) of the generic Phoenix 386 BIOS, let me know.
Should I point out that the 1/15/1988 BIOS ROM I found was for an INTEL chipset? (Intel chipsets in the late 80s were turds but they got serious about it circa 1994)
If you're lucky, you might find a old computer capable of using a 386SX/386DX processor with a generic Phoenix 80386 ROM BIOS from 1989 or 1990.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
If the Cyrix is incompatible, it would probably be grayed out in the PCem configuration setup.
Re: DTK 386SX Clone and Phoenix 386 clone.
One small error in the Phoenix Patch:
Should be:
Code: Select all
"Pheonix 386 clone", ROM_PX386,
Code: Select all
"Phoenix 386 clone", ROM_PX386,
Re: DTK 386SX Clone and Phoenix 386 clone.
I was bound to mess something up. Patch coming tomorrow, I have to go to bed.te_lanus wrote:One small error in the Phoenix Patch:Should be:Code: Select all
"Pheonix 386 clone", ROM_PX386,
Code: Select all
"Phoenix 386 clone", ROM_PX386,
Also, I forgot the NVR patch for DTK386 so CMOS saving will not work.
Re: DTK 386SX Clone and Phoenix 386 clone.
Patch for my patch that added PX386 and DTK386.
Fixes a typo in the Phoenix BIOS selection and adds NVR for DTK386.
Fixes a typo in the Phoenix BIOS selection and adds NVR for DTK386.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: DTK 386SX Clone and Phoenix 386 clone.
Committed to rev 307. I did change the Phoenix clone to use a 1989 BIOS.
Phoenix 486 clone.
Trying to figure out PX486 emulation. I found a BIOS for the exact same chipset as the AMI 486/WinBIOS 486 clones.
The BIOS seems to boot, up to the point that it complains setup settings aren't set. where the keyboard does not work at all.
Coincidentally, this is one of the BIOSes with the nasty 3.2GB HDD bug.
The BIOS seems to boot, up to the point that it complains setup settings aren't set. where the keyboard does not work at all.
Coincidentally, this is one of the BIOSes with the nasty 3.2GB HDD bug.
Last edited by nerd73 on Sat 22 Aug, 2015 10:11 pm, edited 2 times in total.
Re: DTK 386SX Clone and Phoenix 386 clone.
BIOS'es differ as to what scan code set they expect the keyboard to be in during POST. Some require untranslated set 1 (such as the AMI BIOS'es), and some Award BIOS'es require translated set 2. Some are fine with whatever the keyboard is set to.
Re: DTK 386SX Clone and Phoenix 386 clone.
That makes perfect sense. Now which file is the one that defines that?Battler wrote:BIOS'es differ as to what scan code set they expect the keyboard to be in during POST. Some require untranslated set 1 (such as the AMI BIOS'es), and some Award BIOS'es require translated set 2. Some are fine with whatever the keyboard is set to.
Re: DTK 386SX Clone and Phoenix 386 clone.
- nerd73: It's keyboard.c and keyboard_at.c. But thing is, PCem doesn't support anything other than untranslated set 1. Translated set 2 is identical to it but needs the translation bit set in a certain register, otherwise the BIOS will see translation is off and expect untranslated set 2 which differs from both the other two sets.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
I've noticed something with the Phoenix 386 clone.
The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amount of memory in kilobytes.
Also, if you try to select user defined type 48 or type 49 hard disk parameters in the BIOS, the emulated machine will lock up and render the CMOS setup unusable. To correct this, you have to delete the Px386.nvr file, relaunch PCem and recreate it.
The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amount of memory in kilobytes.
Also, if you try to select user defined type 48 or type 49 hard disk parameters in the BIOS, the emulated machine will lock up and render the CMOS setup unusable. To correct this, you have to delete the Px386.nvr file, relaunch PCem and recreate it.
Re: DTK 386SX Clone and Phoenix 386 clone.
I'm pretty sure the PX386 uses XTIDE, right?ppgrainbow wrote:I've noticed something with the Phoenix 386 clone.
The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amount of memory in kilobytes.
Also, if you try to select user defined type 48 or type 49 hard disk parameters in the BIOS, the emulated machine will lock up and render the CMOS setup unusable. To correct this, you have to delete the Px386.nvr file, relaunch PCem and recreate it.
Re: DTK 386SX Clone and Phoenix 386 clone.
the chipsets in 386's couldn't address more than 64MB. It was a hard limit for quite some time in the industry. Even OS/2 needs a special BIOS setting for more than 64MB. 386's shipped with very little RAM, it was expensive back then. Try to stick with specs that existed back then, and you will have MUCH better luck. And a disk that is in the table. Or within the 500MB BIOS limit of the era.ppgrainbow wrote:I've noticed something with the Phoenix 386 clone.
The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amount of memory in kilobytes.
Also, if you try to select user defined type 48 or type 49 hard disk parameters in the BIOS, the emulated machine will lock up and render the CMOS setup unusable. To correct this, you have to delete the Px386.nvr file, relaunch PCem and recreate it.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
Yep. The PX386 uses XTIDE, because the CMOS setup is not 100% usable. And I don't know if using the extended BIOS setup off of a floppy disk will fix the bugs or not. With the XTIDE, it's possible to create a hard disk image up to as much as 8,064 MB...however, MS-DOS 5 through 6.22 will only see 8,025 MB as usable..split into four partitions: the primary 2,047 MB partition and the 5,977 MB extended partition (two 2,047 MB logical drives and one 1,802 MB logical drive).nerd73 wrote:I'm pretty sure the PX386 uses XTIDE, right?ppgrainbow wrote:I've noticed something with the Phoenix 386 clone.
The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amount of memory in kilobytes.
Also, if you try to select user defined type 48 or type 49 hard disk parameters in the BIOS, the emulated machine will lock up and render the CMOS setup unusable. To correct this, you have to delete the Px386.nvr file, relaunch PCem and recreate it.
It would be downright impossible to find any software to run under MS-DOS and 16-bit versions of Windows that will use a drive that large! The best practice for 386-era emulated machines would be to use a hard disk image no larger than 128 MB.
- ppgrainbow
- Posts: 479
- Joined: Thu 04 Sep, 2014 7:03 am
- Contact:
Re: DTK 386SX Clone and Phoenix 386 clone.
That's correct. 386-based chipsets greater than 64 MB and MFM, RLL, ESDI and IDE hard disks larger than 504 MB in capacity (1,024 cylinders, 16 heads, 63 sectors per track) were not available at the time when the Phoenix 386 based chipsets came out in 1989; infact the 386SX versions couldn't even address more than 16 MB (640 KB Base Memory, 15360 KB Extended) due to the 24-bit address limit.neozeed wrote:the chipsets in 386's couldn't address more than 64MB. It was a hard limit for quite some time in the industry. Even OS/2 needs a special BIOS setting for more than 64MB. 386's shipped with very little RAM, it was expensive back then. Try to stick with specs that existed back then, and you will have MUCH better luck. And a disk that is in the table. Or within the 500MB BIOS limit of the era.ppgrainbow wrote:I've noticed something with the Phoenix 386 clone.
The Phoenix 80386 ROM BIOS will max out at 64 MB (640 KB Base Memory, 64512 KB Extended). If I select RAM to allocate higher than 64 MB, the extended memory counter will wrap at 0 KB as it relies on a 16-bit unsigned integer to store the total amount of memory in kilobytes.
Also, if you try to select user defined type 48 or type 49 hard disk parameters in the BIOS, the emulated machine will lock up and render the CMOS setup unusable. To correct this, you have to delete the Px386.nvr file, relaunch PCem and recreate it.
The largest hard disk type specified in the predefined hard disk table is type 32, 127 MB or 1,024 cylinders, 15 heads and 17 sectors per track for a MFM-based hard drive.
Under OS/2 1.3 though 2.1, these versions will not even accept IDE hard disks larger than 504 MB without have to run into boot problems!
Re: DTK 386SX Clone and Phoenix 386 clone.
Sorry for the almost 2 year bump, but I have finally figured out why all the 486 and Pentium Phoenix BIOS'es hang - they enter the CPU into SMM mode by writing to port B2h, but since that isn't emulated at all on PCem, the BIOS is stuck there waiting.nerd73 wrote:Trying to figure out PX486 emulation. I found a BIOS for the exact same chipset as the AMI 486/WinBIOS 486 clones.
The BIOS seems to boot, up to the point that it complains setup settings aren't set. where the keyboard does not work at all.