Mail Archives: djgpp/2000/04/30/00:10:10
>> BIOS... I do not know, how to do that... :-/
>
>Just enter BIOS on startup pressing the DEL key. Than find something that
sounds
>like "IDE HDD AUTO DETECTION". Enter this mode and see what BIOS has
detected.
>After each detection succeeded/failed press the "N" key. Finally quit BIOS
using
>"EXIT WITHOUT SAVING". Post what BIOS has found...
Yet I know what you mean...
But it is not what I mean !!!
The Problem has nothing to do with BIOS and anything like this.
For example: If you install Linux on one partition, you
will find the /tmp directory in the root.
But I do not like to have the /tmp in my root.
So I create a second partition and mount them as /tmp.
No problem if it on a second Harddisk, because if I
remove the second harddisk, Linux can not mount the
partition and use the default...
No data will lost.
I have the same problem with a /data partition.
In Dos it is a problem, because you can set only one
TEMP variable. So I need to make a test whether the
Partition is there or not. Please note, that I have no
directory (because Linux) on the TEMP-Partition.
The other and bigger problem are the DATA-Partitions.
My Program try to write to f: but it is not there !!!
The Program ends in a crash...
Biggest Problem: the LOG-Files partition !!!
Now I like to Test the Harddisk dns if it exist, they
must look for the partition whether it is there or not.
Commandline is:
SET temp=c:\tmp # set the default TEMP dir
chk4part f:\tmp # check the partition and dir
IF ERRORLEVEL 1 SET temp=f: # set the new temp env-var
where chk4part my program is which check for the partition.
Please note that if you try from the commandline "dir m:"
and the Partition is not there you get a error message.
I must supress any error messages in my programs.
And the chk4part.exe must be seperately from the program.
Thanks for your help
Michelle
--
Don't cc: me on mailinglists, I'm subscribed, if I write there.
----------------------------------------------------------------------------
Linux rebootet man in drei Fällen:
Neuer Kernel, neue (Board-)Hardware, Stromausfall....
Aber Windows rebootet man auch in drei Fällen:
Schutzverletzung, Bluescreen, keinen Bock...
- Raw text -