Stuart Meier wrote:
>
> <beta mode is ON>
> !
>
> OK, it will not run normally, but it will run in a DOS box (badly) in a
> FULL SCREEN dos window (ie not maximised but full screen). Unfortunately
> it WON'T generate an ASM file, and the screen sometimes has partial
> characters or funny symbols (triangles etc) eg when you hit f7.

THANKS for the feedback, it's really nice. :o)

> Only way I have found to get it to generate an asm is to reboot into
> plain DOS, but then I have to reboot into Windows etc to do anything
> else....

Hmm that sounds buggy. I didn't do much
checking on the program, just put it up in
a hurry and thought that if anyone wanted to
use it they would probably tell me what changes
they wanted, and nobody showed much interest
at the time so I got on with other projects.

I understand there is a video issue, my program
tries to write direct to the video card and
seems to be incompatible with some of the new
"superior" operating systems.

> * Are you running Windows or perhaps Linux etc Roman? Should it run
> under Windows?

Yes it should, provided windows can run a fairly
simple dos app. The .asm file write is very
straightforward using the Borland fprintf function
to a text file so the only reason I can think for
failing in the file write is maybe it was just
latched up from the video issues??

> * My 1.1 sec WAV has been padded with 2secs of FFs. Not sure why. Easy
> to edit off the RETLWs of course.

That would be the header of the wave file, you
might be getting some funny data right at the
start too? Mostly I use raw sound data so it
didn't bother me. :o)

> Anyway Roman it is VERY good, and will certainly prove useful.

Thanks! I had a fun and frantic couple of days
there working on it.

> Only
> thought so far is whether the code could be compressed eg by something
> like run-length encoding - ie for slow changing parts,
>
> instead of
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>      retlw b'01010101'   ; 55
>
> have 8*(retlw b'01010101'   ; 55 )
>
> in some way....but it means a duration multiple for every bit I guess

Absolutely! My original ideas for compression
went right out the window whan I saw the
generated output with the large strings of 01
repeated, and you're right that would be the
first avenue of compression. The next would
probably be the 0000 and 11111 strings, being
short would probably involve a PCX type RLE
trick??

> ----- Original Message -----
> From: "Stuart Meier" <stuartmeier@ryg1.freeserve.co.uk>

> > Can't get encoder to display properly (well, barely at all)...when I
> run
> > it, screen blanks

I'll check if I set the graphics stuff to VESA,
but apart from that there's not a lot I can do
as it's a graphics library thing. One day i'll
get some windows (linux?) programming stuff and
transfer some of my old utilities. One day. ;o)
-Roman

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads