Date:	Mon, 3 Nov 1997 20:23:03 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Andrew Crabtree <andrewc AT rosemail DOT rose DOT hp DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Incompatibilities with NT
In-Reply-To:	<01bce882$b4ee2630$45111d0f@ros51675cra.rose.hp.com>
Message-ID:	<Pine.SUN.3.91.971103201517.16348E-100000@is>
MIME-Version:	1.0

On Mon, 3 Nov 1997, Andrew Crabtree wrote:

> CCase                 999984  487984   512000     49%   m:/

So DJGPP *does* see m:\ !

> >I have no idea
> >how this setting is done on NT, or even *if* it exists.  A call to
> >`setdisk' will return the last possible drive.
> >Don't bother.  It seems that NT doesn't know about TRUENAME.
> It appears NT doesn't have a setdisk either.

No, I meant the `setdisk' function from the DJGPP libc.

>  Perhaps I can make a small
> prog that uses the sources from dj's libc for setdisk and truename?

Good idea.  Compile `_truename.c' with -DTEST, and you get your program.

> >But you should be able to say "net use" and see where M: is mapped.
> >I'd expect `df' to print the same mapping for M:, unless something is
> >VERY wrong.
> Doesn't look promising.
> 
>              M:        \\view\                   Atria Multi-Version FS

No, actually it seems quite OK.

> >SUBST'ed drive.  I attach the info from the Interrupt List below; it
> >would be interesting to see whether this function tells anything
> >useful about your M: drive.
> I'll play around with nasm and see if I can remember how to program real
> mode assembly.

Just use __dpmi_int in a C program compiled with DJGPP.  No need to go to
assembly (unless you want to). 

What kind of problems did you have accessing files on that drive?  Can 
you tell me which error messages did you see, and from what utilities 
(Make? gcc? ld?).  Until now, we saw that `df' works OK with m:.  (It 
might be that some low-level libc function needs to be fixed, and you 
will live happily ever after, if we only find that function.)

- Raw text -