![]() However the kernel naturally is different as this does support multiple users. By default Citrix is setup for async terminals, and as far as I can find there was no actual LAN connection product available. This is just simply the most common setup of the era, where UNIX was typically deployed with async terminals, and with remote users on dialup. The Citrix media I have is dated from January 25th, 1991. Although according to the ‘ official timeline (pdf)‘ version 1.0 was released in 1990. This was just after the protected mode version of Windows was demo’d to Bill Gates & Steve Balmer, which incentivized Microsoft to dump OS/2 for Windows. This put Citrix in a bad position as they had setup their product strategy around the next generation OS from Microsoft which had for all intents and purposes had been made obsolete overnight. And as the Windows 3.0 juggernaut picked up steam selling over 4 million copies, while all previous versions of Windows combined were only in the neighborhood of 2 million copies. As far as I’m aware, none of the OS/2 1.x sales numbers were ever released.Ĭitrix 1.0 is limited to OS/2 1.2 character mode executables. And there simply isn’t that many. And with the industry moving to the aforementioned graphical Windows 3.0 applications Citrix hit the market with a thud. Citrix provides support for the following applications: I’ll have to ask people smarter than me about finding any of this information.Īnyways Citrix requires that you install it onto a HPFS partition. Citrix uses the Microsoft OS/2 1.21 kernel + base level for the OS. After installing and running syslevel on both they report the same level. The Citrix Support Bulletin Board has further information on these techniques, along with specific code examples that you can tailor to your specific needs. Microsoft C 6.0, as an example, also provides instructions and make-files for rebuilding the libraries. Many compilers such as Microsoft C 6.0 make available the source to the runtime library. For example, if your application makes heavy use of long arithmetic, you can modify the multiply and divide runtime functions to use the explicit 32-bit multiply and divide instructions available on the 386 and 486 processors, thereby avoiding the 32-bit arithmetic emulation. However, we have found that it is a simple matter to boost performance by replacing some of your compiler runtime library routines. ![]() Unfortunately, this prevents natural optimization for the 386 32-bit environment. The compilers available for MS OS/2 generally supply library functions which will execute on both 286 and 386 processors because MS OS/2 will run on these. You can take advantage of this fact to boost performance of your application while running on MULTIUSER. Because of this Citrix MULTIUSER runs only on 386 compatible processors. MULTIUSER is designed to take advantage of the 386/486 instruction set where possible. Ne2k: ioaddr=0x320,irq=10, mac=fe:fd:00:00:00:01, ethmod=nullĬitrix has many 386 hooks in place. After applying the CSD MU01091 I saw this in the readme: Vgaromimage: file=bios/VGABIOS-elpin-2.40Īta0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14Īta0-master: type=disk, path=”citrix500.img”, cylinders=1023, heads=16, spt=63Ĭom1: enabled=1, mode=socket-server, dev=localhost:8880Ĭom2: enabled=0, mode=socket-server, dev=localhost:8881Ĭom3: enabled=0, mode=socket-server, dev=localhost:8882Ĭom4: enabled=0, mode=socket-server, dev=localhost:8883 ![]() I’m using this as a template for a config. Naturally to boot floppy image it’ll need a change. While I’m waiting for a 5 1/4″ disk, I thought I’d take a crack at installing Citrix Multiuser version 1.0 that had surfaced a while back. As this ancient promotional video shows, the product they were chasing was low end Unix market, oddly enough their larger competition being SCO Xenix, which itself was separated out from Microsoft.
0 Comments
Leave a Reply. |