🚀 go-pugleaf

The easy way: Put this line in your Autoexec.bat file:

CALL C:\PROGRA~1\BORLAND\JBUILD~1\BIN\SETVARS.BAT C:\PROGRA~1\BORLAND\JBUILD~1 /a

Don't use long filenames! ! ! ! ! (If you have installed somewhere else - adjust the paths)
Of course it takes a  a few bytes of memory (resident)- but who cares today as long as it works.
--
Yours

Poul Bak
(You are welcome to respond by mail, just remove the 'REMOVEUPTO. ' from the address !)

Life is too short to reinvent the wheel just because you don't like the color - use a hub cap and
get on with your life!


"Dave Bird" <dave@xemu.demon.co.uk> skrev i en meddelelse news:zLlu3sEqZdn5EwTm@xemu.demon.co.uk...
> In article <cTen5.7936$541.1365842@juliett.dax.net>, Tomas Andersen
> <tomasand@c2i.net> writes
> >I am not sure if this is what you are looking for
> >but I use this method:
>
>  I found something relevant in the JBuilder help.  It doesn't
>  frigging work :-( . This really inspires confidence :-( :-( .
>
>  For a start, it has changed from "jbuilder" to "jbuilder2".
>
>  setvars.bat says [rightly] if you have zero parameters that
>  it needs parameters, and [wrongly] if you have more than zero
>  parameters that it has too many parameters.
>
>  Edit the main part of it into makevars.bat and it then works;
>  except you have to increase the environment space as shown.
>
>  Even then, go to c:\jbuilder2\myclasses\TheApp and
>  try to do  c:java TheApp   and it can't find TheApp.class...
>  which exists.
>
>
>  Is this beta software?  it came in a box, with a license,
>  and I paid for it :-( :=( :-( .  [I know it's huge. I can't
>  imagine how you'd check it all for consistency. But putting
>  it out unworking and inconsistent in any obvious part....]
>
>
>
> [:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>
>
> Setting environment variables for command-line tools
>
> The environment paths for the command-line environment are defined
> separately from the
> environment paths for the IDE. The SOURCEPATH and CLASSPATH environment
> variables must be set so the command-line tools can find the classes
> required for your program. The standard JBuilder setting for the class
> path includes several directories and zip files in the jbuilder\
> directory. You might need to run jbuilder\bin\setvars.bat to set the
> environment variables for the command line.
>
> To set your environment variables:
>
>    Open a DOS window.
>    Go to the JBuilder\bin directory.
>    Type setvars c:\jbuilder (assuming JBuilder is on drive C).
>    You can use the set command to compare your environment variables
>      before and after running setvars.bat.
>
> You should not issue the setvars.bat command more than once in a DOS
> session, because every time the command is issued, additional
> environment space is used.
>
>
> Setting the DOS environment space
>
> When you issue the setvars.bat command at the DOS prompt, you might get
> an Out Of Environment Space error, because only a small amount of
> environment space is allocated by default.
>
> To increase the DOS environment space:
>
>    In the DOS window, click the control menu in the upper left,
>     and choose Properties.
>    Click the Memory tab to show the Memory options page.
>    In the Initial Environment drop-down list, select a reasonably
>     large value, such as 2048.
>    The other settings in the page can be left at Auto.
>    Click OK to close the Properties dialog, and type exit at the prompt,
>     to quit the DOS session.
>    Start a new DOS session.
>
> You should now be able to issue the setvars.bat command successfully.
>
> Note: These instructions apply to Windows 95 only; they do not apply
> to Windows NT.
>
>
>
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::]
>
> --
>    ^-^-^-@@-^-;-^   http://www.xemu.demon.co.uk/
>         (..)__u     news:alt.smoking.mooses