Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,600 of 4,255    |
|    mutazilah@gmail.com to All    |
|    chromebook    |
|    16 Feb 23 11:47:19    |
      From: muta...@gmail.com              I'm having a bit of trouble getting my head around       the Chromebook.              This device seems unique in that it allows a custom       BIOS to be flashed, ie Seabios.              On an old Chromebook, I have used this:              https://mrchromebox.tech              and been able to run PDOS/386. And it's great.              However, INT 14H doesn't give me anything because       I don't have a serial port.              I asked the Seabios people if they could add a TCP/IP       stack (they already have a USB stack) plus NDIS so that       they could do USB tethering to an Android smartphone,       to give me a virtual modem.              They weren't interested.              I'm interested in replacing Seabios with my own BIOS       where I can add these things to a public domain project       instead of someone else's copyrighted project.              This should revive communications not just for PDOS/386,       but also MSDOS, which I think uses INT 14H.              My understanding is that by going this route I would be       using documented standards - something that I can't do       with wifi.              But I'm interested in what the flashed BIOS itself would       need to look like.              I'm guessing I could have the RM16 INT 14H switch to       PM32 and then manipulate the hardware (USB port),       the same way as a normal driver for any hobbyist OS       would do it.              My understanding is that a USB stack is a lot of work,       so I probably won't embark on such a project for a long       time, but I would like to make sure that appropriate       hardware exists and that this is a reasonable way       forward to revive modems for legacy OSes.              Neither Windows nor Linux would be required on the PC.              There would still be an Android phone, but it is merely       acting as part of an elaborate modem. The OS itself is       not exceeding the capabilities of computers available       in 1986.              Any idea how many lines of C code are required to have a       BIOS good enough to run PDOS/386? With and without a       modem (ie breakdown of different components).              Also, how portable is the BIOS to the different Chromebooks?              Thanks. Paul.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca