1. was wondering...
Hi, I was wondering if it would be possible that someone could convert the
linux for euphoria version into a redhat rpm file...I keep trying to run
these euphoria programs from the console, and get nothing...I just installed
an older copy of slackware, and get nothing at the prompt.
Slackware will decipher rpm files, and they include the necesary system
setup stuff right?
Maybe I should just install my debian instead...
Monty in Oregon
2. Re: was wondering...
If anyone needs information on RPM to convert to RPM distributions
http://www.rpm.org
Bernie
3. Re: was wondering...
Monty writes:
> I keep trying to run these euphoria programs from the console,
> and get nothing...I just installed an older copy of slackware,
> and get nothing at the prompt.
I hope you tried alpha release #3, uploaded a couple of
days ago. It works a lot better for some people who
just saw a new prompt appear when they ran a
Euphoria program. It also fixes a problem with
Euphoria's rand() function on some systems.
rand() is used in a lot of the demos -
allsorts.ex, buzz.ex, sanity.ex, lw.ex, etc.
Regards,
Rob Craig
Rapid Deployment Software
http://members.aol.com/FilesEu/
4. Re: was wondering...
On Sat, 10 Jul 1999, you wrote:
> Hi, I was wondering if it would be possible that someone could convert the
> linux for euphoria version into a redhat rpm file...I keep trying to run
> these euphoria programs from the console, and get nothing...I just installed
> an older copy of slackware, and get nothing at the prompt.
> Slackware will decipher rpm files, and they include the necesary system
> setup stuff right?
> Maybe I should just install my debian instead...
> Monty in Oregon
--
Hi Monty:
Building an rpm is not very easy, and it is unnecessary for a program which
has already been compiled (like the Euphoria package). All that's needed is
tar to unpack things in the right directories.
If you are using the latest version of RedHat, most likely the problem lies
somewhere other than the installation.
To track down why things don't work, it would help to compare some things,
like:
where are your euphoria files located? Mine for example are in:
/home/irv/euphoria
cd euphoria
$ ls
Editor/ demo/ euphoria/ html/ install.doc tutorial/
bin/ doc/ include/ readme.doc
Note: the Editor directory is Dave's EE. The rest of the files and
directories are installed by tar when Euphoria is unpacked.
I have set full world read/write permissions on the euphoria directory,
just to keep things simple. Also the exu program has full permissions.
Next, check your path settings:
$ echo $PATH
and
$ echo $EUDIR
/home/irv/euphoria
Next, type exu <return> you should see:
Euphoria 2.1 Public Domain Edition (pre-alpha #3) for Linux.
Copyright (c) Rapid Deployment Software 1999
Permission is freely granted to anyone to copy and
redistribute this Public Domain Edition of Euphoria.
file name to execute?
If the few settings above are correct, you should get the message shown
above. Let us know what happens - so we can go from there.
Irv
5. Re: was wondering...
I wrote:
> where are your euphoria files located? Mine for example are in:
> /home/irv/euphoria
> cd euphoria
> $ ls
> Editor/ demo/ euphoria/ html/ install.doc tutorial/
> bin/ doc/ include/ readme.doc
>
> Note: the Editor directory is Dave's EE. The rest of the files and
> directories are installed by tar when Euphoria is unpacked.
>
Further correction: the euphoria subdirectory is mine, not a part of the
Euphoria installation.
Irv
6. Re: was wondering...
- Posted by MB King <boot_me at GEOCITIES.COM>
Jul 11, 1999
-
Last edited Jul 12, 1999
Irv,
I tried what you said, and got all of the correct answers, but I hadn't
given full permissions to the euphoria directories and sub-directories, but
that didn't help either. I was wondering if it was because I wasn't
actually using a ext2 file system on this, but a umsdos file system, but
when I installed that older copy (slackware 96) it was on an ext2
filesystem, and it didn't work there either.
Anyway, it didn't help any. Still nothing happens.
I read that Slackware tries to be the most Posix complient of the bunch,
wonder if that is it???
I have been trying to install a copy of Debian that I had laying around
and was doing great up until I got to the make a boot disk part, then it
gave up the ghost. I was going "Wow, this thing installs like a charm, wish
Slackare had been like that" right up to that point (The final and most
important point, as I am using it as a second hard disk), and want the boot
disk to boot past Winblows, so I can download stuff onto my Win hard disk,
and then mount it and copy it up to the Linux disk, but retain my hard disk
as is with no modifying.
Anyway, a friend of mine has already burned me a Redhat 6.0 disk and I
will have it QUITE soon. Still would be interesting to know if I am doing
something wrong, or if it is an incompatibility.
Thanks again
Monty
7. Re: was wondering...
On Mon, 12 Jul 1999, you wrote:
> Irv,
><snip>
> Anyway, a friend of mine has already burned me a Redhat 6.0 disk and I
> will have it QUITE soon. Still would be interesting to know if I am doing
> something wrong, or if it is an incompatibility.
> Thanks again
> Monty
That should solve the problem. I've heard good comments about Debian,
also, so if you can get the latest version, you may like it.
Good luck,
Irv
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
8. was wondering...
Hi to all reading this,
I was wanting to share data between a windows program and a dos
program, using peek and poke, such as was described in this posting by Kevin
Sieger:
>...made a small program to allocate
>100 bytes of memory and I allowed for input of a string. The program
>then poked this string into memory at the allocated position. I then
>had it pass the address and number of bytes to a file, and ended the
>program with wait_key (so program would not end, will have something
>better later ;}!). I then created another program that read the memory
>location and number of bytes from the created file, and peeked at that
>location with the info, and WALA!! It displayed the string I inputted.
>This was done under win95...
I was wondering, does anyone know what a good memmory address to do this at
would be? I have a general knowledge of how to do it, such as directed
above, and was planning on using it to talk from a dos game I am working on
to another dos game or server through a windows tcp program written with
Eusock.
Thanks in advance...
Monty
9. was wondering...
Does anyone know how to get a background image to scroll using Pete E.'s
modex utility? I have gotten the background I want to display... but have a
hard time understanding what I need to do to get the next chunk of data and
move it into the screen. Here is some code...
--try to write over a spot on the visible screen
--source screen is named "monty"
--destination is "screen"
constant chunk = new_command(copy, {0,0,width,height,0,0})
set_source_pos(chunk, {dx,0})
set_dest_pos(screen, {0,0})
I am having a hard time understanding how to use this constant. It bears
some resemblance to how the constants are used in the win32lib, which I
can't quite understand either. You can't define the constant in a
procedure, I do know how you can call the constant, such as with
call(chunk) in this case, but a constant is an unchanging amount right? So
once you define the constant as having one set of data in it, you cannot
redefine it right? I can't call it from a procedure...
I have a feeling that I should be able to maybe use
set_source_pos(chunk, {dx,0})
set_dest_pos(screen, {0,0})
call(chunk)
and that would move a chunk of bitmap to the visible screen.
Help I'm stuck!
Any help would be appreciated.
Monty in Oregon
10. Re: was wondering...
On Tue, 21 Apr 1998, Monty King wrote:
> Does anyone know how to get a background image to scroll using Pete E.'s
> modex utility? I have gotten the background I want to display... but have a
> hard time understanding what I need to do to get the next chunk of data and
> move it into the screen. Here is some code...
>
> --try to write over a spot on the visible screen
> --source screen is named "monty"
> --destination is "screen"
> constant chunk = new_command(copy, {0,0,width,height,0,0})
>
> set_source_pos(chunk, {dx,0})
> set_dest_pos(screen, {0,0})
>
> I am having a hard time understanding how to use this constant. It bears
> some resemblance to how the constants are used in the win32lib, which I
> can't quite understand either.
The constant simply holds the "handle" to the command. Since you don't
change the handle, I made it a constant in the demos. (The handle is
actually a pointer to the machine codes that execute the command, so it
could be declared as an atom)
atom chunk
chunk = new_command(copy, {0,0,width,height,0,0})
> You can't define the constant in a
> procedure, I do know how you can call the constant, such as with
> call(chunk) in this case, but a constant is an unchanging amount right? So
> once you define the constant as having one set of data in it, you cannot
> redefine it right?
The handle is constant; the memory it points to is not.
> I can't call it from a procedure...
If you mean you can't declare the constant in the procedure, then use an
atom as I have above.
> I have a feeling that I should be able to maybe use
>
> set_source_pos(chunk, {dx,0})
> set_dest_pos(screen, {0,0})
> call(chunk)
>
> and that would move a chunk of bitmap to the visible screen.
>
>
> Help I'm stuck!
> Any help would be appreciated.
> Monty in Oregon
>
Why does my code always come back to haunt me?
--
_____ _____ _____
________ /\ \ /\ \ /\ \
/ \ \ / \____\ / \____\ / \____\
/ _ \____\ / / ___/_ / /____/ / / ___/_
/ / \ |____|/ / /\____\ / \ \ / / /\____\
\ \_/ / / \ \/ / ___/_\ \ \ \ \/ / ___/_
\ /____/ \ / /\ \\/\ \ \ \ / /\ \
\ \ \ \ \/ \____\ \ \ \ \ \/ \____\
\ \ \ \ / / \ \____\ \ / /
\ \____\ \ / / \ / / \ / /
\ / / \ / / \/____/ \ / /
\/____/ \/____/xseal at harborside.com\/____/
11. Re: was wondering...
Monty wrote:
>I am having a hard time understanding how to use this constant. It =
bears
>some resemblance to how the constants are used in the win32lib, which I
>can't quite understand either.=20
Regarding the Win32Lib constant, it's a 'handle', along the same lines =
of a file handle - something that lets Win32Lib know what object you are =
referring to in your function. By analogy:
puts( "hi there" )
doesn't have enough information to display, because Euphoria needs to =
know what device is being referred to. You need to include the specific =
device:
puts( Screen, "hi there" )
In the same way:
wPuts( "hi there" )
doesn't have enough information, because it doesn't know what window or =
control to write to. You need to include the handle:
wPuts( MyWindow, "hi there" )
In "real" Win32 calls, the handle is something called a "device =
context". "hDC" is shorthand for "handle to the device context". From =
the Win32 help file:
"A device context is a structure that defines a set of graphic objects =
and their associated attributes, and the graphic modes that affect =
output. The graphic objects include a pen for line drawing, a brush for =
painting and filling, a bitmap for copying or scrolling parts of the =
screen, a palette for defining the set of available colors, a region for =
clipping and other operations, and a path for painting and drawing =
operations."
In short, a device context contains all the information Win32 needs to =
know about how to write to something: what object is being referred to, =
it's current font, it's text color, it's pen thickness, it's drawing =
mode, and so forth.
Working with a DC is a bit complex. Like a file, it needs to be opened =
before you can use it, and closed when you are done with it. When you =
close a DC, it "forgets" it's prior settings. There *is* an option for =
having a DC remember it's settings after closure, but at an additional =
overhead of about 800K per window.
In any event, Win32Lib attempts to shield you from this, by letting you =
pass it's own window handle instead. The value for Win32Lib's handles is =
just an index to an internal data structure that it maintains with =
information about the type of window, the attributes, and so on. So the =
first handle value that Win32Lib will return is 1, the second is 2, and =
so forth.
Internally, Win32Lib converts the handle into a DC by looking it up. The =
value was stored in the window_handle structure when the window (or =
control) was created:
global function getHandle( integer iWin )
return window_handle[ iWin ]
end function
For some reason (probably because it's "fuzzy headed" Tuesday) I'm a bit =
unclear on when exactly a hDC needs to be released, so I won't go into =
further details and make a total fool of myself. In the =
soon-to-be-released next version of Win32Lib, I've gotten rid of the =
persistant text and graphics, so things are a bit more complex. I used =
to defer everything into the WM_PAINT event. Now, everything is done "on =
demand", and is a bit more complex to optimize.
-- David Cuny
