Message-ID: <37944FC9.89B57A6A@swipnet.se>
From: Anders David Skarin <hobbit AT swipnet DOT se>
X-Mailer: Mozilla 4.5 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Problems whith passing commandline args
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 22
NNTP-Posting-Host: 130.244.42.10
X-Complaints-To: news-abuse AT swip DOT net
X-Trace: nntpserver.swip.net 932466718 130.244.42.10 (Tue, 20 Jul 1999 12:31:58 MET DST)
NNTP-Posting-Date: Tue, 20 Jul 1999 12:31:58 MET DST
Organization: A Customer of Tele2
X-Sender: s-437261 AT dialup42-1-10 DOT swipnet DOT se
Date: Tue, 20 Jul 1999 12:30:33 +0200
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hello!

Dear list :-)

I have a strange problem (at least if i define it), when 
passing command line arguments longer than 2 characters (+3 dos file
type)
to my 3d-engine my vesa routines will not find the mode i 
want to use. (this works perfectly if you pass 2+3 char arguments)

The only thing i can think of that might be causing the problem 
is DJGPPs internal transfer buffer (__tb), which I use to collect
mode/card
information in my vesa routines. 

Does anyone know if DJGPP uses this buffer for commandline args, 
and in the process somehow corrupts it?

If this is the case, how does one get the size of the buffer to clear
it?

Or does anyone have the slightest clue of what else might be going on?