On 30/08/2025 08:06, c186282 wrote:
On 8/30/25 1:54 AM, rbowman wrote:
On Fri, 29 Aug 2025 23:51:17 GMT, Charlie Gibbs wrote:
It was for us. We needed all that memory. It was only a few years ago >>>> that I finally got rid of all the hacks I wrote in to normalize
pointers
and deal with segment wrap-arounds. It was horrible. Forget the 640K >>>> barrier - the 64K barrier was alive and well on the 8086/8088/80286.
Tiny, Small, Large, Bigger & Humongous. I have the names wrong but I'm
pretty sure there were 5 sets of libraries that you had to chose to do a >>> build. Then there was what was referred to as the 'thunk' in DJGPP
circles
when you need to get real.
Tbe original 8088 had all the needed registers.
Could minimum deliver at LEAST an easy 64k code
space and at LEAST another 64k data area. A few
tricks and .......
So YEA - you COULD run some kind of -IX on
the original PCs. Not super fast/efficient
but it COULD work. Remember early versions
of SCO.
286/386 ... MUCH better - but it came LATER.
The big trouble was that Unix was expanding faster than the PC
architecture could handle until the 386 made it all easy.
Then SCO Unix made it all not just possible, but extremely handy.
But we never got a serious graphical user interface on Unix. By the time
X windows had stabilised and cent window managers evolved Linux had
arrived.
On 8/30/25 3:28 AM, The Natural Philosopher wrote:
On 30/08/2025 08:06, c186282 wrote:
On 8/30/25 1:54 AM, rbowman wrote:
On Fri, 29 Aug 2025 23:51:17 GMT, Charlie Gibbs wrote:
It was for us. We needed all that memory. It was only a few years >>>>> ago
that I finally got rid of all the hacks I wrote in to normalize
pointers
and deal with segment wrap-arounds. It was horrible. Forget the 640K >>>>> barrier - the 64K barrier was alive and well on the 8086/8088/80286.
Tiny, Small, Large, Bigger & Humongous. I have the names wrong but I'm >>>> pretty sure there were 5 sets of libraries that you had to chose to
do a
build. Then there was what was referred to as the 'thunk' in DJGPP
circles
when you need to get real.
Tbe original 8088 had all the needed registers.
Could minimum deliver at LEAST an easy 64k code
space and at LEAST another 64k data area. A few
tricks and .......
So YEA - you COULD run some kind of -IX on
the original PCs. Not super fast/efficient
but it COULD work. Remember early versions
of SCO.
286/386 ... MUCH better - but it came LATER.
The big trouble was that Unix was expanding faster than the PC
architecture could handle until the 386 made it all easy.
Agreed.
Then SCO Unix made it all not just possible, but extremely handy.
Well ... not "handy" enough.
My boss at the time - a very smart nerd - and I did
discuss DOS -vs- Unix for The Outfit.
We eventually decided on DOS, and ultimately Win.
MORE stuff. MORE support.
But we never got a serious graphical user interface on Unix. By the
time X windows had stabilised and cent window managers evolved Linux
had arrived.
Hey, DEALT with 'X' and WMs on the first versions
of Linux you could get. NOT super-easy all the time.
Spent like 48 hours getting it to rec my damned mouse
with RH.
NOT encouraging.
However Linux GOT BETTER. Soon I had all the needed
office servers on Linux - Just Because.
But, alas, the Staff - Winders Forever And Always.
Typical "split environment".
On 30/08/2025 10:30, c186282 wrote:
On 8/30/25 3:28 AM, The Natural Philosopher wrote:
On 30/08/2025 08:06, c186282 wrote:
On 8/30/25 1:54 AM, rbowman wrote:
On Fri, 29 Aug 2025 23:51:17 GMT, Charlie Gibbs wrote:
It was for us. We needed all that memory. It was only a fewTiny, Small, Large, Bigger & Humongous. I have the names wrong but I'm >>>>> pretty sure there were 5 sets of libraries that you had to chose to >>>>> do a
years ago
that I finally got rid of all the hacks I wrote in to normalize
pointers
and deal with segment wrap-arounds. It was horrible. Forget the >>>>>> 640K
barrier - the 64K barrier was alive and well on the 8086/8088/80286. >>>>>
build. Then there was what was referred to as the 'thunk' in DJGPP
circles
when you need to get real.
Tbe original 8088 had all the needed registers.
Could minimum deliver at LEAST an easy 64k code
space and at LEAST another 64k data area. A few
tricks and .......
So YEA - you COULD run some kind of -IX on
the original PCs. Not super fast/efficient
but it COULD work. Remember early versions
of SCO.
286/386 ... MUCH better - but it came LATER.
The big trouble was that Unix was expanding faster than the PC
architecture could handle until the 386 made it all easy.
Agreed.
Then SCO Unix made it all not just possible, but extremely handy.
Well ... not "handy" enough.
My boss at the time - a very smart nerd - and I did
discuss DOS -vs- Unix for The Outfit.
We eventually decided on DOS, and ultimately Win.
MORE stuff. MORE support.
I was the boss. SCO Unix for the networked servers and Win 3 for the desktops
SUN PC-NFS to hang it all together.
I waited. By around 2003 Debian had some sort of GUIBut we never got a serious graphical user interface on Unix. By the
time X windows had stabilised and cent window managers evolved Linux
had arrived.
Hey, DEALT with 'X' and WMs on the first versions
of Linux you could get. NOT super-easy all the time.
Spent like 48 hours getting it to rec my damned mouse
with RH.
NOT encouraging.
However Linux GOT BETTER. Soon I had all the neededYup. Of course
office servers on Linux - Just Because.
But, alas, the Staff - Winders Forever And Always.
Typical "split environment".
I was the boss. SCO Unix for the networked servers and Win 3 for the
desktops SUN PC-NFS to hang it all together.
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 926 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 497226:31:10 |
| Calls: | 15,771 |
| Calls today: | 13 |
| Files: | 5,333 |
| D/L today: |
18 files (8,192P bytes) |
| Messages: | 678,463 |