X-Apparently-From: Message-ID: <000b01c09608$0092cf60$4d822a40@dbcooper> From: "Patrick Moran" To: References: <01FD6EC775C6D4119CDF0090273F74A4021F4D AT emwatent02 DOT meters DOT com DOT au> Subject: Re: DR-MOUSE, DPMS (was Hard Disk 20gb and dos) Date: Tue, 13 Feb 2001 11:17:12 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Reply-To: opendos AT delorie DOT com ----- Original Message ----- From: "da Silva, Joe" To: Sent: Monday, February 12, 2001 8:24 PM Subject: RE: DR-MOUSE, DPMS (was Hard Disk 20gb and dos) > Incidentally, I mentioned the above because you seemed > to be saying you used QEMM to load DRMOUSE, so I > thought you meant QEMM's equivalent to 'LH' ... I no longer use QEMM. However, QEMM does use it's own loadhigh to load the mouse, but it has the initial size wrong and you can squeeze it into the B000-B7FF range by setting ot to the correct number of bytes needed to load. > Don't know about that ... I never did get multitasking to work > properly, so I never had this problem ... :-/ There are a few things you ned to change in the TM .INI file for communications. This is in a TID that I uploaded and is on one of the DRDOS sites. I need to upload that again with the final version I put together which eliminates all of the duplicates. I also have the Novell Personal Netware and DRDOS 6 TIDs. > > Also I will firce some things to load low when using Personal Netware to > > get the most use of upper memory. I let VLM do it's thing but paly with > > the rest such as LSL.COM. The DRDOS memory manager is not too > > intelligent (like QEMM is) and I have to play around with the small > > drivers and TSRs to get the best results when using the server. The > > client does not take that much. However, DRDOS memory manager is a lot > > smarter than MSDOS's. > > > [da Silva, Joe] > > Why not use Novell's 32 bit drivers, instead? They load into > extended memory, so you can load lots more goodies into > the UMB ... What drivers are these and where can I get them. VLMs do load into extended memory, but the server portion loads into memory below 1MB. With all the TSRs and Drivers I have, there is not enough space in upper memory to load all of the server components. I think I have something like about 73K of UMB left in conyigious space at the end of the UMB area to work with. > > Did anyone actually contact Lineo about this? Since it is not a major > > upgrade, I don't see how they can change Novell's policy on this. They > > would have had to purchase the license intact and since Novell made it > > freely available to anyone, I don't see how Caldera/Lineo can/could > > change it. If it were version 7.1 or something, maybe they could. > > > [da Silva, Joe] > > Yes ... well I have always been disappointed by > Caldera/Lineo. They have certainly never lived up > to their initial indications about where they would > take DR-DOS! Remember how the whole source > was going to be available? Remember the TCP/IP > stack, web browser, LFN and FAT32 support that > was promised? > > IMHO, Caldera/Lineo's only real interest in DR-DOS > was to have something with which to sue Micro$oft. > Evidence : > Day 1 - Caldera acquires DR-DOS. > Day 2 - Caldera files it's suit against Micro$oft. > Day N - Caldera and Micro$oft settle. > Day N+1 - Cladera virtually stops DR-DOS development. You are right about that. I knew that was the mail reason that Caldera bought DRI stuff from Novell. It was very obvious from the beginning. I was glad to see that someone had the guts to put MS in their place and would like to see the government break it up into tiny little peices, so that we cab use decent operating systems and applications. Everyone writes their apps and stuff for MS OSes. They don't bother with Linux, MAC, Solaris, BeOS, and many other popular operating systems and especially DOS. Lineo says they are dropping because of the popularity of Ebbeded Linux. Personally, I don't believe them. Enbdded DOS has been very popular for decades now and is still currently being used and there are still a lot of Z-80 embedded systems being used and built. Most embedded stuff does not need 32bit power. These are dedicated systems to do small industrial tasks. We would take a single board Z-80 that would mount on a 5-1/4" floppy drive and use either Z-80 Assemby or BASIC to program them. They are still popular today. PIC is also very popular and that is 8 and 16 bit technology and is very good for these applications and have a lot of power and are cheap to build. You can use simm 30 sockets to mount the components and plug in modules you design into a simple backplane. You do not even have to use multilayer pc-boards! Double sided at the most. We upgraded a whole steel mill to automation using 8 bit PLCs, Microcontrollers and PCs from S-100 CP/M-80, OSI-4P, Commodore C-128, Apple ][e, TI-99/4, IBM PC and XTs, with a few ATs and a couple of 386SX's. Most of the PCs were just used as terminals anyway. (And of course we played games on them!!!) Industrial control systems do not need the sophisticated 386 and higher technology. There would be a lot of benefts from using Linux in a plant wide environment and use Embedded Linux, however, what plants are going to change over from WINDOZE crap? Pat _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com