1] Problems with compiler 2] Problems with Rhide -- Update More info

[Ethan Rosenberg]

Thanks to all for your help and suggestions. I am a newbie, so I
might not understand everything you say.

1] Compiler -

Problems was options. Object code location was originally set to
D:\DJGPP\BIN. Since the D: drive did not exist, it defaulted. Now
set to C:\D\DJGPP\BIN, and it compiles.

->>However, on attempting a build, it is looking for a project [this
test program is not part of a project], which it cannot find, and
defaults. I've tried "Close Projects" but that does not seem to
help. Suggestions please.

1) I think RHIDE expects a project for all programs, even if they are
stand alone w/o any external subroutines. How do I turn off this option?
What is the latest release of RHIDE?

2] RHIDE -

I am again using my wife's computer to test the DOS 7.1 [I'm
switching drives between her Windows 2000 and my DOS 7.1]. She has
an ATI Radeon VE video card.

->> Is it possible that I do not have the correct DOS Drivers for that card?

1) A cursory internet search seems to verify this as the
problem. Does anyone know of a source for these drivers. They are
not on the AMD/ATI site.

2) An old problem with RHIDE: When I ask for help [F1], RHIDE
crashes. Is there any fix?

Thanks in advance.

Ethan

[Alexei A. Frounze]

Post by Ethan Rosenberg
Thanks to all for your help and suggestions. I am a newbie, so I
might not understand everything you say.

...

Post by Ethan Rosenberg
2] RHIDE -
I am again using my wife's computer to test the DOS 7.1 [I'm
switching drives between her Windows 2000 and my DOS 7.1]. She has
an ATI Radeon VE video card.
->> Is it possible that I do not have the correct DOS Drivers for that card?
1) A cursory internet search seems to verify this as the
problem. Does anyone know of a source for these drivers. They are
not on the AMD/ATI site.

Never heard of video drivers for DOS. The VGA video BIOS must be good
out of the box and no drivers should be needed. Too bad if it's not.

Alex

[Ethan Rosenberg]

Post by Ethan Rosenberg

Post by Ethan Rosenberg
Thanks to all for your help and suggestions. I am a newbie, so I
might not understand everything you say.

...

Post by Ethan Rosenberg
2] RHIDE -
I am again using my wife's computer to test the DOS 7.1 [I'm
switching drives between her Windows 2000 and my DOS 7.1]. She has
an ATI Radeon VE video card.
->> Is it possible that I do not have the correct DOS Drivers for

that card?

Post by Ethan Rosenberg
1) A cursory internet search seems to verify this as the
problem. Does anyone know of a source for these drivers. They are
not on the AMD/ATI site.

Never heard of video drivers for DOS. The VGA video BIOS must be good
out of the box and no drivers should be needed. Too bad if it's not.
Alex

Thanks Alex, even if it was bad news.

[Rod Pemberton]

Post by Ethan Rosenberg

Post by Ethan Rosenberg

Post by Ethan Rosenberg
Thanks to all for your help and suggestions. I am a newbie, so I
might not understand everything you say.

...

Post by Ethan Rosenberg
2] RHIDE -
I am again using my wife's computer to test the DOS 7.1 [I'm
switching drives between her Windows 2000 and my DOS 7.1]. She has
an ATI Radeon VE video card.
->> Is it possible that I do not have the correct DOS Drivers for

that card?

Post by Ethan Rosenberg
1) A cursory internet search seems to verify this as the
problem. Does anyone know of a source for these drivers. They are
not on the AMD/ATI site.

Never heard of video drivers for DOS. The VGA video BIOS must be good
out of the box and no drivers should be needed. Too bad if it's not.

Thanks Alex, even if it was bad news.

"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers don't implement
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

That makes me wonder if your ATI Radeon VE card is old enough that it lacks
VESA video modes. But, that shouldn't be the case:

"Register compatible with VGA "
"BIOS compatible with VESA for super VGA "

and supports:
640x480,800x600,1027x768,1152x864,1280x1024,1600x1200,1920x1080,1920x1200,19
20x1440,2048x1536 in 256,64k,256k colors

If it was, you could've tried Scitech's UNIVBE drivers which adds VESA modes
for S/VGA only cards. If the VESA is broken, they still might work if the
card is register compatible with one of the older video chipsets, such as
the S3 Trio. On the other hand, if someone could post what video modes
RHIDE attempts to use, you might be able to test the modes on your card with
WHATVGA, part of the VGADOC package, to see if the card has a problem or if
it's missing some mode.


Rod Pemberton

[Ethan Rosenberg]

Post by Rod Pemberton

Post by Ethan Rosenberg

Post by Ethan Rosenberg

Post by Ethan Rosenberg
Thanks to all for your help and suggestions. I am a newbie, so I
might not understand everything you say.

...

Post by Ethan Rosenberg
2] RHIDE -
I am again using my wife's computer to test the DOS 7.1 [I'm
switching drives between her Windows 2000 and my DOS 7.1]. She has
an ATI Radeon VE video card.
->> Is it possible that I do not have the correct DOS Drivers for

that card?

Post by Ethan Rosenberg
1) A cursory internet search seems to verify this as the
problem. Does anyone know of a source for these drivers. They are
not on the AMD/ATI site.

Never heard of video drivers for DOS. The VGA video BIOS must be good
out of the box and no drivers should be needed. Too bad if it's not.

Thanks Alex, even if it was bad news.

"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers don't implement
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html
That makes me wonder if your ATI Radeon VE card is old enough that it lacks
"Register compatible with VGA "
"BIOS compatible with VESA for super VGA "
640x480,800x600,1027x768,1152x864,1280x1024,1600x1200,1920x1080,1920x1200,19
20x1440,2048x1536 in 256,64k,256k colors
If it was, you could've tried Scitech's UNIVBE drivers which adds VESA modes
for S/VGA only cards. If the VESA is broken, they still might work if the
card is register compatible with one of the older video chipsets, such as
the S3 Trio. On the other hand, if someone could post what video modes
RHIDE attempts to use, you might be able to test the modes on your card with
WHATVGA, part of the VGADOC package, to see if the card has a problem or if
it's missing some mode.
Rod Pemberton

Ron -

Thank you.

I was able to download Scitech's "SNAP Graphics for DOS" which are
DOS drivers for video cards. There is NO instructions with the
download, and THE COMPANY IS OUT OF BUSINESS. Can anyone give me
some guidance, please, and walk me thru what has to be done.

Thanks again.

Ethan

[Rod Pemberton]

Post by Ethan Rosenberg
I was able to download Scitech's "SNAP Graphics for DOS" which are
DOS drivers for video cards.

Correct company, wrong software. Try this here:
http://www.scitechsoft.com/ftp/sdd/univbe67.exe

Boot into DOS. Don't use a Windows console. If your card or compatible
register set can't be found, you'll get "No supported SuperVGA chip
detected!"

If that's the case, you could try to find out what modes your card and RHIDE
support. But, at that point it's probably easier to just buy or trade for
another vid card...

Post by Ethan Rosenberg
THE COMPANY IS OUT OF BUSINESS.

Nope, http://www.scitechsoft.com/


Rod Pemberton

[Ethan Rosenberg]

Post by Rod Pemberton

Post by Ethan Rosenberg
I was able to download Scitech's "SNAP Graphics for DOS" which are
DOS drivers for video cards.

http://www.scitechsoft.com/ftp/sdd/univbe67.exe
Boot into DOS. Don't use a Windows console. If your card or compatible
register set can't be found, you'll get "No supported SuperVGA chip
detected!"
If that's the case, you could try to find out what modes your card and RHIDE
support. But, at that point it's probably easier to just buy or trade for
another vid card...

Post by Ethan Rosenberg
THE COMPANY IS OUT OF BUSINESS.

Nope, http://www.scitechsoft.com/
Rod Pemberton

Ron -

Thanks.

Downloaded and installed in DOS. Only supports 16 bit DOS. DOS 7.1
is 32 bit DOS. The SNAP Graphics will support 32 bit DOS and the ATI
Radeon VE 7000 card, which is what we have. Once I open SNAP in DOS,
then what? How will I know which driver to use? Even if it auto
detects the video card, don't I need some lines in autoexec.bat and config.sys?

Again, thanks.

Ethan

[Rod Pemberton]

Post by Ethan Rosenberg
Downloaded and installed in DOS. Only supports 16 bit DOS.

DOS is only 16-bits. So what is the problem?

Post by Ethan Rosenberg
DOS 7.1
is 32 bit DOS.

The question is why do you think DOS 7.1 is 32-bits?

DOS 7.1 which came with Windows 95B/95C/98/SE are all 16-bit DOS. I'm
currently running 7.1 myself. It's not 32-bits when booted into instead of
Windows. It's not 32-bits when run as a Windows console or "DOS-box". The
usual way to get 32-bit support is by some form of 32-bit extension such as
VCPI, DPMI, custom coding, etc. DPMI hosts include a Windows console or
"DOS-box", DJGPP DPMI application, OpenWatcom DPMI application, etc.

Post by Ethan Rosenberg
The SNAP Graphics will support 32 bit DOS and the ATI
Radeon VE 7000 card, which is what we have.

I see cards similar to yours, but not yours specifically:
http://www.scitechsoft.com/chiplist/snap_linux_chiplist.html

Post by Ethan Rosenberg
The SNAP Graphics will support 32 bit DOS and the ATI
Radeon VE 7000 card, which is what we have.

There are no complete 32-bit DOS-es that I'm aware of. Freedos-32 is close,
but incomplete.

Post by Ethan Rosenberg
The SNAP Graphics will support 32 bit DOS and the ATI
Radeon VE 7000 card, which is what we have.

I'm not familiar with SNAP Graphics. It's very possible that the SNAP
Graphics may have 32-bit graphic routines or 32-bit DPMI/VCPI support for
16-bit DOS.

Post by Ethan Rosenberg
Once I open SNAP in DOS,
then what? How will I know which driver to use? Even if it auto
detects the video card, don't I need some lines in autoexec.bat and config.sys?

I don't know. There are a few versions of SNAP. Since, you want DOS, I'm
assuming, since you didn't state so, that you've downloaded the SNAP
Graphics IES version? Well, I'll poke around into the versions and see what
I can find...


Rod Pemberton

[Rod Pemberton]

Post by Ethan Rosenberg

Post by Ethan Rosenberg
Once I open SNAP in DOS,
then what? How will I know which driver to use? Even if it auto
detects the video card, don't I need some lines in autoexec.bat and

config.sys?
I don't know. There are a few versions of SNAP. Since, you want DOS, I'm
assuming, since you didn't state so, that you've downloaded the SNAP
Graphics IES version? Well, I'll poke around into the versions and see what
I can find...

I didn't think I had RHIDE, but I do. RHIDE seems to use simple text modes
on my video card. No VESA or anything special, AFAICT. With a quick
glance, I didn't see any method to change or identify the video mode it is
using. This seems to be inaccurate:

"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers don't implement
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

I must _thank_ everyone who failed to supply the video modes used by
RHIDE...


When you startup RHIDE, what happens?

rhide

Have you tried:

rhide -b
rhide -S


As for SNAP, I tried their version named "snap-dos-3.1.1.exe." This
appears to be an incomplete demonstration version to me. I.e., you have to
buy a complete version to install drivers, not just test them out... It
installs some executables and a hidden file "io32.sys". Unfortunately, it
says the complete documentation is in some other file. The .exe
gareport.exe should identify your card, just run it:

gareport

There are some other useful programs which allow you to test the card and
change driver options. This is all in the README.TXT.


Rod Pemberton

[Alexei A. Frounze]

On Sep 8, 2:17 am, "Rod Pemberton" <***@nowhere.cmm> wrote:
...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers don't implement
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?

Alex

[Ethan Rosenberg]

Post by Rod Pemberton
...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers

don't implement

Post by Rod Pemberton
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?
Alex

Alex -

First to all on the list, my apologies for misunderstanding and
thinking that DOS 7.1 was a 32 bit system.

Second, I am not sufficiently conversant/competent to try to compile
and run the code you provided. If you would kindly provide an .exe
file with instructions, it would be appreciated. Since I eventually
will be able to run RHIDE on my computer, which may not have a
problematic video card, I would like to be able to retain the
original copy of RHIDE.

Much thanks to all.

Ethan

[Alexei A. Frounze]

Post by Ethan Rosenberg

Post by Rod Pemberton
...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers

don't implement

Post by Rod Pemberton
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?
Alex

Alex -
First to all on the list, my apologies for misunderstanding and
thinking that DOS 7.1 was a 32 bit system.
Second, I am not sufficiently conversant/competent to try to compile
and run the code you provided. If you would kindly provide an .exe
file with instructions, it would be appreciated. Since I eventually
will be able to run RHIDE on my computer, which may not have a
problematic video card, I would like to be able to retain the
original copy of RHIDE.
Much thanks to all.
Ethan

OK, to make it extremely clear...
Rename the original rhide.exe to rhide0.exe
download http://alexfru.narod.ru/RHIDE.EXE to where rhide0.exe is.
Run rhide.exe.
Report what you got.

Alex

[Ethan Rosenberg]

Post by Rod Pemberton

Post by Ethan Rosenberg

Post by Rod Pemberton
...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the

screen contents

Post by Ethan Rosenberg

Post by Rod Pemberton

Post by Rod Pemberton
and mode-specific settings, and some SVGAs and video drivers

don't implement

Post by Rod Pemberton
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?
Alex

Alex -
First to all on the list, my apologies for misunderstanding and
thinking that DOS 7.1 was a 32 bit system.
Second, I am not sufficiently conversant/competent to try to compile
and run the code you provided. If you would kindly provide an .exe
file with instructions, it would be appreciated. Since I eventually
will be able to run RHIDE on my computer, which may not have a
problematic video card, I would like to be able to retain the
original copy of RHIDE.
Much thanks to all.
Ethan

OK, to make it extremely clear...
Rename the original rhide.exe to rhide0.exe
download http://alexfru.narod.ru/RHIDE.EXE to where rhide0.exe is.
Run rhide.exe.
Report what you got.
Alex

Alex -

Thank you.

Did it. Regrettably, no improvement. Slightly more checker board.

Any other ideas?

FYI - The ATI Radeon VE 7000 has the capacity to use two(2)
monitors. I do not know if that helps.

A different video card is not an option. This is my wife's
computer, and she needs the existing video card.

Ethan

PS I thank everyone for all their input and help.
++++++++++++++

[Alexei A. Frounze]

Post by Ethan Rosenberg

Post by Rod Pemberton

Post by Ethan Rosenberg

Post by Rod Pemberton
...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the

screen contents

Post by Ethan Rosenberg

Post by Rod Pemberton

Post by Rod Pemberton
and mode-specific settings, and some SVGAs and video drivers

don't implement

Post by Rod Pemberton
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?
Alex

Alex -
First to all on the list, my apologies for misunderstanding and
thinking that DOS 7.1 was a 32 bit system.
Second, I am not sufficiently conversant/competent to try to compile
and run the code you provided. If you would kindly provide an .exe
file with instructions, it would be appreciated. Since I eventually
will be able to run RHIDE on my computer, which may not have a
problematic video card, I would like to be able to retain the
original copy of RHIDE.
Much thanks to all.
Ethan

OK, to make it extremely clear...
Rename the original rhide.exe to rhide0.exe
downloadhttp://alexfru.narod.ru/RHIDE.EXEto where rhide0.exe is.
Run rhide.exe.
Report what you got.
Alex

Alex -
Thank you.
Did it. Regrettably, no improvement. Slightly more checker board.
Any other ideas?
FYI - The ATI Radeon VE 7000 has the capacity to use two(2)
monitors. I do not know if that helps.
A different video card is not an option. This is my wife's
computer, and she needs the existing video card.
Ethan
PS I thank everyone for all their input and help.
++++++++++++++

Well, if that didn't help, then something else is additionally broken.
I don't know what. I could dig and figure it out, but I'm not going to
do it. Sorry.

If you have windows on that computer (which I think you do) and that's
windows 2000/XP/2003/Vista (not 95/98/Me), you could try to install
either Microsoft Virtual PC 2007 or VMWare Server (both are freely
available on the internet), create a virtual machine in there, install
DOS and DJGPP in there and work in the VM. That might work (unless
something's broken in those virtualizing products and DJGPP doesn't
work well in there -- I think I tried once but that wasn't extensive
use of DJGPP in a VM, so YMMV).

Other options for the same hardware:
- use a different IDE or just a plain text editor for editing, use
plain gdb for debugging and compile the code from the command line
(directly, through a script or makefile). I know it can be painful to
give up on a handy IDE and instead use something more primitive, but
it's a possible option. I, for one, rarely use IDEs and debuggers. I
use a powerful text editor, make files (or equivalent scripts) and
manage to figure out most of bugs in newly written code w/o the
debugger. It varies with older code or code written by others.
- entirely different set of tools, something for windows, unless you
absolutely must code for DOS or need direct hardware access. Btw, if
you don't care much about modern C++ and can live in a 16-bit world,
you can download Borland's Turbo C++ 1.01 and use it. RHIDE was
designed after Borland's IDEs of their C/C++ and Pascal compilers for
DOS.

Alex

[Ethan Rosenberg]

Post by Alexei A. Frounze

Post by Ethan Rosenberg
Alex -
Thank you.
Did it. Regrettably, no improvement. Slightly more checker board.
Any other ideas?
FYI - The ATI Radeon VE 7000 has the capacity to use two(2)
monitors. I do not know if that helps.
A different video card is not an option. This is my wife's
computer, and she needs the existing video card.
Ethan
PS I thank everyone for all their input and help.
++++++++++++++

Well, if that didn't help, then something else is additionally broken.
I don't know what. I could dig and figure it out, but I'm not going to
do it. Sorry.
If you have windows on that computer (which I think you do) and that's
windows 2000/XP/2003/Vista (not 95/98/Me), you could try to install
either Microsoft Virtual PC 2007 or VMWare Server (both are freely
available on the internet), create a virtual machine in there, install
DOS and DJGPP in there and work in the VM. That might work (unless
something's broken in those virtualizing products and DJGPP doesn't
work well in there -- I think I tried once but that wasn't extensive
use of DJGPP in a VM, so YMMV).
- use a different IDE or just a plain text editor for editing, use
plain gdb for debugging and compile the code from the command line
(directly, through a script or makefile). I know it can be painful to
give up on a handy IDE and instead use something more primitive, but
it's a possible option. I, for one, rarely use IDEs and debuggers. I
use a powerful text editor, make files (or equivalent scripts) and
manage to figure out most of bugs in newly written code w/o the
debugger. It varies with older code or code written by others.
- entirely different set of tools, something for windows, unless you
absolutely must code for DOS or need direct hardware access. Btw, if
you don't care much about modern C++ and can live in a 16-bit world,
you can download Borland's Turbo C++ 1.01 and use it. RHIDE was
designed after Borland's IDEs of their C/C++ and Pascal compilers for
DOS.
Alex

Alex -

Thank you for all your efforts.

I am not a good enough programmer to be able to write code just using
a text editor. I need to write a segment, compile and write the next segment.

I have two(2) hard drives in this computer, one with Windows 2000 and
mine with DOS 7.1. Sometimes, to transfer files I run the DOS drive
as a slave of the Win 2000 drive. Otherwise, they are run
independently. I have DOS 7.1 for the FAT32,. so I do not have to
partition the drive. The problem I know is with the video card. If
I run "edit", and exit the program, the top of the screen remains
blue. I am trying to avoid replacing the video card, for the
aforementioned reason, since additionally, I will have my own
computer, with a video card which will probably work very well with RHIDE.

Thanks again.

Ethan

[Rod Pemberton]

...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the screen contents
and mode-specific settings, and some SVGAs and video drivers don't implement
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point.

faq22 seems inaccurate to me. RHIDE is only using text modes, AFAICT. I
haven't trapped the interrupts to confirm, but I'd seriously question why an
application would use special VESA functions for text modes. That would be
a serious coding offense, if not error, in my book. DJGPP has text
functions to save and restore screen contents.

Anyway, I have no need for RHIDE, so I'm probably about done trying to help
Ethan here...

and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?

You might just want to put an .exe on one of your sites. No offense
intended to Ethan, but it appears he has very little experience with any of
this... I noticed it seemed he hadn't tried much of what I suggested
either.


Rod Pemberton

[Alexei A. Frounze]

Post by Rod Pemberton

...

Post by Rod Pemberton
"RHIDE uses advanced VESA functions to save and restore the screen

contents

Post by Rod Pemberton
and mode-specific settings, and some SVGAs and video drivers don't

implement

Post by Rod Pemberton
these functions very well."
http://www.delorie.com/djgpp/v2faq/faq22_1.html

Exactly my point.

faq22 seems inaccurate to me. RHIDE is only using text modes, AFAICT. I
haven't trapped the interrupts to confirm, but I'd seriously question why an
application would use special VESA functions for text modes. That would be
a serious coding offense, if not error, in my book. DJGPP has text
functions to save and restore screen contents.
Anyway, I have no need for RHIDE, so I'm probably about done trying to help
Ethan here...

and the reason why I provided the source code for the
program that allows to run RHIDE on "problematic" cards. If nobody
tried that, do I need to e-mail the executable (or post in UUENCODE/
BASE-64) or is there enough info and intelligence already on how to
get an .exe from the source?

You might just want to put an .exe on one of your sites. No offense
intended to Ethan, but it appears he has very little experience with any of
this... I noticed it seemed he hadn't tried much of what I suggested
either.
Rod Pemberton

Fair enough. Let's give it a shot: http://alexfru.narod.ru/RHIDE.EXE
-- the original RHIDE.EXE must be renamed to RHIDE0.EXE.

Alex

[Ethan Rosenberg]

Post by Rod Pemberton
When you startup RHIDE, what happens?
rhide
rhide -b
rhide -S

===========
Ron -

Post by Rod Pemberton
When you startup RHIDE, what happens?
rhide

I get a normal screen, but when I start editing, or especially open
one of the menu options, I get checkerboard.

Post by Rod Pemberton
rhide -b
rhide -S

Yes. No change.

Ethan

[G***@seagate.com]

Ethan Rosenberg <***@earthlink.net> wrote on Mon, 10 Sep 2007 08:56:17
-0400:

# I am not a good enough programmer to be able to write code just using
# a text editor. I need to write a segment, compile and write the next
segment.

Write a simple Makefile for it:

foo.exe: my.c another.c something.cpp
gcc -o foo.exe my.c another.c something.cpp

Then do your editing in a modern IDE like CodeWright, SlickEdit,
Code::Blocks, Eclipse, etc. - and then for your Build command use:

bash -c make

(This assumes all DJGPP environment variables are already set up - you
probably will need to set HOME and SHELL.)

In my case, I have a DJGPP.BAT which sets up all appropriate
environment variables, then if parameter is supplied just runs them.
I should post it, perhaps it will be useful to others... in another
message though.