| delorie.com/archives/browse.cgi | search |
| From: | cat AT animal DOT u-net DOT com |
| Subject: | Re: Loading ramdrive.sys |
| Organization: | none |
| References: | <39F7DEBC DOT 7938A452 AT ma DOT tum DOT de> |
| Newsgroups: | comp.os.msdos.djgpp |
| NNTP-Posting-Host: | host1.lowtech.org |
| X-Original-NNTP-Posting-Host: | host1.lowtech.org |
| Message-ID: | <39f84c2f$1@news.gemsoft.net> |
| Date: | 26 Oct 2000 16:22:23 GMT |
| X-Trace: | 26 Oct 2000 16:22:23 GMT, host1.lowtech.org |
| Lines: | 15 |
| X-Complaints-To: | abuse AT gemsoft DOT net |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
I have had great help from this group in setting up a means of running DJGPP binaries from Ramdisk, and I am working on a sort of installer (with a customised stub written in a very old version of Turbo-C .. tcc). There is one question however. If the original computer has several partitions on its hard disk the ram drive may not be drive D:. Is there a simple way of finding out which drive the ramdrive really is after installation ? A suitable DOS or BIOS interrupt call would be a very simple solution in this case. Tony Goddard http://www.d4maths.co.uk
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |