javispedro1 wrote on 2024-08-12, 09:16:

The p386 does NOT support LBA, so you cannot exceed this 8GiB limit with any DOS version, nor 9x. Other non-DOS bases OSes like Linux or NT may be able to exceed the 8GiB limit (booting it being a problem...). Another workaround would be to use a DDO, or a custom BIOS.

Doesn’t support LBA at all? Bios seems to be LBA aware and bootup indicates an LBA status.

I just assumed it was an early implementation (pre-LBA22?).

It doesn't support int13x. As some other posters were pointing out there is some confusion about what "LBA" means, but in this BIOS it just means ECHS.

Wondering if biospatcher works.
Should avoid all these headaches

What are people using as serial terminal software in MS-DOS or Windows 3.11 (hyperterminal?)? I might want to use the Pocket 386 for embedded systems serial communication work. Thanks.

i recall "COMit" was popular bitd, but a somewhat large choice can be had from simtel.

https://www.infania.net/misc/simtelnet/msdos/commprog.html

javispedro1 wrote on 2024-08-12, 09:16:

The per-disk int13 limit is 1023 cylinders, not 2GB. Depending on the BIOS this may be 500 MiB or 8GiB. As the p386 BIOS supports ECHS, the limit is 8GiB (slightly more).
The p386 does NOT support LBA, so you cannot exceed this 8GiB limit with any DOS version, nor 9x. Other non-DOS bases OSes like Linux or NT may be able to exceed the 8GiB limit (booting it being a problem...). Another workaround would be to use a DDO, or a custom BIOS.

I'd love to get my hands on some of the old industrial systems using the DM&P for just that reason. I'd know at least one on sight. Sadly it looks like anyone selling them online (so far) 'knows what they have' and is trying to make sure they'll always have it 😀. Likely trying to sell to manufacturing users that want the same part.

Who knows, maybe I'll luck out and find one in junked industrial kit at one of the assorted VCFs or the other VCF's events.

Dunno why you'd want more than 8GB. On a 8GB CF I can install more 386-usable OSes than I count with my fingers and still have ridiculous amount of space to spare for each of them.

Anyway, I do agree that overall a better CPU would ironically make for a more interesting 386-era machine than the pocket386; in the same way that the pocket386 itself makes for a better book8088 than the book8088 😀
(Albeit the NEC V20 on the book8088 helps...)

I want to install DOS Box on my Windows 10 machine before I put Open Watcom on the Pocket 386. Does this page describe a method you would recommend?

http://nuclear.mutantstargoat.com/articles/re … ng/dos01-setup/

What does ~Dos mean? Does the tilde refer to the C:\ root directory of my Windows 10 PC?

Is there an easier method? Thanks.

simon_e_hall wrote on 2024-07-02, 12:19:

Gave in and got one of these, after trying to tell myself I didn't need it! […]
Show full quote

Gave in and got one of these, after trying to tell myself I didn't need it!

So backed up the CF and then put it in a safe place, and created a fresh install on a Transcend Industrial 2GB card, which apparently worked okay, until I tried to get Adlib sound which did not work, Wolf 3D did not detect it.

So being the only thing I changed, tried another CF card, a Cisco 512mb card and the Adlib is detected!

So any ideas what is going on? Not a show stopper just need to test some different CF cards.

Has anyone else had this issue, I have now experimented with different sizes of cards and Operating Systems, regardless of the operating system if I go past a 512MB CF Card, (i.e. 1GB, 2GB) the Adlib will not work.

My adlib worked with the supplied 2gb card out of the box. I would compare the primary hard drive settings auto -detected for each. Is it always LBA on, 32bit off, PIO Mode 4?

simon_e_hall wrote on 2024-08-20, 07:46:

Has anyone else had this issue, I have now experimented with different sizes of cards and Operating Systems, regardless of the operating system if I go past a 512MB CF Card, (i.e. 1GB, 2GB) the Adlib will not work.

I do not see how that would be possible. When you say "multiple Operating Systems", which do you mean? And how are you testing whether the Adlib works or not?

Standard MS-DOS using the Adlib jukebox, OS/2 Warp 3 using the OPL3 driver, (also NT3.51 but that crashes after logon) it will not detect the adlib with anything over a 500mb CF card. Also Windows 3.1 although not an operating system using the default Adlib driver. 5o0MB CF Card and everything works as expected.

Hardware settings are always the same, i.e. LBA on, 32-bit off, etc.

Good to know I am not being stupid as I cannot see a reason why it would affect it.

Now looking at your comments I have not used the actual supplied CF Card (just imaged it and put it in a safe place), might be worth trying that...

Been doing a bit of fault finding regarding my weird issue of no Ad Lib sound with CF cards, plugged in the original 2gb and that worked, so thought it maybe an issue with certain manufactures, so created a number of drives on 2gb all the way up to 8gb, and the issue only seems to happen to Transcend cards, which is the majority of CF cards I use! But again, cannot figure out why, interesting little issue though.

simon_e_hall wrote on 2024-08-28, 11:21:

Been doing a bit of fault finding regarding my weird issue of no Ad Lib sound with CF cards, plugged in the original 2gb and that worked, so thought it maybe an issue with certain manufactures, so created a number of drives on 2gb all the way up to 8gb, and the issue only seems to happen to Transcend cards, which is the majority of CF cards I use! But again, cannot figure out why, interesting little issue though.

I still can't imagine WHY it would make a difference but maybe look beyond the bios AUTO values and see what Transend is using for stuff like Heads, Cylinders, Sectors. There is probably a DOS utility which could help if BIOS doesn't save them switching from auto to manual.

BinaryDemon wrote on 2024-08-28, 12:56:

simon_e_hall wrote on 2024-08-28, 11:21:

Been doing a bit of fault finding regarding my weird issue of no Ad Lib sound with CF cards, plugged in the original 2gb and that worked, so thought it maybe an issue with certain manufactures, so created a number of drives on 2gb all the way up to 8gb, and the issue only seems to happen to Transcend cards, which is the majority of CF cards I use! But again, cannot figure out why, interesting little issue though.

I still can't imagine WHY it would make a difference but maybe look beyond the bios AUTO values and see what Transend is using for stuff like Heads, Cylinders, Sectors. There is probably a DOS utility which could help if BIOS doesn't save them switching from auto to manual.

I have no idea WHY either, just does not make sense. Already tried something similar, had another system look at the CHS and transferred them across, but there is no difference between what auto detects and the other system detects. Thought maybe it was because I was transferring an image of the drive (VHD to CF) and maybe I had used a similar but wrong image, but that was not the case.

Even plugged a floppy controller into the ISA adapter and formatted the drive the traditional method but same issue.

Just going to chalk this one up to an oddity and not use Transend cards with it.

A thought occurs to me here, after answering a question in a different thread.

Apple commissioned a bunch of bonafide microdrives for their first gen ipod minis. These would be slow, but would better hold up to swapping hell. (In theory.)

They are reasonably cheap as industrial salvage.

https://eoe.works/products/6gb-hitachi-microd … -2nd-generation

(For example)

In case anyone wants to try one instead of industrial ATA mode flash disk.

simon_e_hall wrote on 2024-08-21, 09:35:

OS/2 Warp 3 using the OPL3 driver, (also NT3.51 but that crashes after logon)

Unrelated but our of curiosity is there really a OPL3-only driver for OS/2? The stock drivers I tried all seem to be expecting some accompanying PCM device, e.g. soundblaster, and refuse to load if only the opl is present.

javispedro1 wrote on 2024-09-04, 09:42:

simon_e_hall wrote on 2024-08-21, 09:35:

OS/2 Warp 3 using the OPL3 driver, (also NT3.51 but that crashes after logon)

Unrelated but our of curiosity is there really a OPL3-only driver for OS/2? The stock drivers I tried all seem to be expecting some accompanying PCM device, e.g. soundblaster, and refuse to load if only the opl is present.

Yes, believe it was this one I used. I also tried to extract the driver from the stock drivers (e.g. Crystal) but had no luck either, but the one below worked a charm.

https://hobbesarchive.com/?detail=/pub/os2/sy … L3_Midi_1-0.zip

Hello, I'm jumping in this thread now that I have a Book 8088 and a Pocket 386 in my posession.

The book 8088 has been wonderful and I have no real complaints yet of the top of my head.
The pocket386 is amazing as well, but it came with 3.1 instead of 95 despite the listing information. Whatever, I installed 95 myself. Then realized I broke 3.1. So i installed 3.1 again.. and broke 95...
So I tried reformatting the CF card with DOS 6.22.

Now I'm stuck with this error
" Drive Not Ready
Insert BOOT diskette in A:
"

I know the CMOS gets cleared when the lion is low/dead. I had disabled the floppy and enabled ps2 with no problems... until now.

Anyone have an idea of why this error is appearing? I have tried modifying the CMOS several times with no luck.

Please excuse the low quality images.
I have tried setting a hard drive delay. Tried the CF card form my book 8088 with another DOS install (was previously working on the 386 and still works on the 8088). No luck with anything.