From: "Mark & Candice White" Newsgroups: comp.os.msdos.djgpp References: <9nppvi$2c8g$1 AT pandora DOT alkar DOT net> Subject: Re: addressing question Lines: 30 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: Date: Sun, 16 Sep 2001 07:00:39 GMT NNTP-Posting-Host: 24.19.84.198 X-Complaints-To: abuse AT home DOT net X-Trace: news2 1000623639 24.19.84.198 (Sun, 16 Sep 2001 00:00:39 PDT) NNTP-Posting-Date: Sun, 16 Sep 2001 00:00:39 PDT Organization: Excite AT Home - The Leader in Broadband http://home.com/faster To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Try asking in news:/alt.os.assembly news:/alt.os.development They are groups more geared tword OS development. Making a segmented 32bit OS on x86 CPUs is not easy. GCC and its dos port DJGPP are made for flat mem models where ds,es,fs,gs,ss all point to the same mem, and cs is all so the same phisical mem. I was going to suggest http://rdos.net/eng/ but it is all in asm, most likely because it is hard to find a C compiler that will work in such an environment. What is wrong with a near pointer to viedo mem? With multi user &| tasking you will want to have the OS send things to the screen(s) not the user, so having just a pointer (near or far) to the screen is in the end a bad idea anyways. With paging and other protection methods used in many OSes like linux, minix, winnt(most un*x), etc... you can have multi user space without relocation of apps, and many other things. Stop in at the news groups I listed above and let us know what you want to do. There is bound to be someone working on something close enough to your idea who can point you in the right direction. There will also be many who can let you know about other options you might not have concidered.