Re: SAAEmu 0.61
You can use Wordpad to read the RTF, if your Word can't do it.
I use RTF because its functionality is 100% the same as DOC's one,
and RTF files are 5-8 times shorter than DOC ones, since DOC uses
unicode.
No, you are wrong. RTF functionality is not 100% the same as DOC
functionality. No, really, REALLY. Trust me here. Show me an RTF document
that supports revision marking, for example.
True, RTF files are 5-8 times smaller than DOC ones. This is because the
RTF
files have 5-8 times less crap in them. Which in turn is because the RTF
format supports 5-8 times fewer features than the DOC format.
I read in Word's docs that RTF can handle anything what DOC can handle.
That's all I know. I'm affraid revision marking is not the think I need to
make
a documentation for my software.
When I write anything which contains @, it is passed as e-mail address.
I tried this. I couldn't recreate it at all.
I tried creating documents in Word, Wordpad and Notepad and loading them
into Word, Wordpad and Notepad. And not once did any of the email
addresses
I put in the document have the stupid { HYPERLINK
mailto:[EMAIL PROTECTED] }codes
Please don't call it stupid. Just upgrade your software and you'll see.
You just said yourself that you have (and use) Wordpad. Why not use
wordpad
to create the .RTF file in the first place?
In fact, you could even load the .RTF file into Wordpad, select all, CUT,
new document, PASTE, and then resave, to remove any strange control codes
like { HYPERLINK }
I used Wordpad to create that file, then I add some lines in Word.
Now both Wordpad and Word shows that so-called stupid hyperlinks correctly.
I must say again: You have some old software (Win95 or NT 4?).
When distributing documentation, you should always make sure that whoever
is
receiving your software is able to actually read that documentation!
Standard .RTF format is a safe bet. As in : what Wordpad does. Not : what
Word says it does.
If you have some official documentation which says what is or what is not
standard, I can use it.
D a v e
Aley
Re: SAAEmu 0.61
From: Simon Cooke [EMAIL PROTECTED]
Umm... given that to my knowledge, Microsoft invented and maintains the
RTF
format, I think they're authorized to extend it in any way they feel fit.
IMNSHO, of course.
Simon
Ok, I stand corrected.
It's a shame, then, that they didn't make Word forwardly compatible with new
extensions to the RTF format ... they could've just made Word ignore unknown
tags (the { HYPERLINK } tag) rather than spew up Error! Bookmark Not
Defined.
I guess the documentation could easily be published as HTML though. Or even,
hey, raw text.
Re: SAAEmu 0.61
From: Dave Hooper [EMAIL PROTECTED]
Ok, I stand corrected.
It's a shame, then, that they didn't make Word forwardly compatible with
new
extensions to the RTF format ... they could've just made Word ignore
unknown
tags (the { HYPERLINK } tag) rather than spew up Error! Bookmark Not
Defined.
I guess the documentation could easily be published as HTML though. Or
even,
hey, raw text.
I believe that the hyperlink tag was originally used in the Windows Help
system, and in RTF files to indicate a local link in a document. Because the
older version of word doesn't recognise http:// tags, it tries to bind the
HYPERLINK tag to an anchor in the current document - which it can't find, so
it gives you an error instead.
Cool, huh? :)
Si
Re: SAAEmu 0.61
1. Credits? No problem. I will do the changes to let you sleep better. Ok. Thanks, 2. Get a later Word version. No. I am a poor student (That excuse used to work anyway. Doesn't actually apply now that I am no longer a student nor poor) 3. I don't know your web address. Well, you should, because it was in the flipping email that you just replied to! Read it again, paying extra-special attention to the words that said http://www.geocities.com/stripwax/ In fact, you could even just link to http://www.geocities.com/stripwax/saasound.zip * B U T * I cannot guarantee that this will always work (I may change the name of the .zip package, for example, when I release my source code) and so I'd rather you just link to the /stripwax/ Latest version is 2.05 but I will be releasing 2.06 in a day or so. (Found some bugs in - guess what - my envelope controller code. Again. In particular, you may have noticed that the 'single decay' envelope was sounding more like a 'single decay and then a very long loud note' envelope .. :) 4. Message CPU halt... is by Z80 CPU emulator. I can't say more, since I have never got this one. When you ask: Is there a bug? I must say: Yes, it looks like a bug. Yes. It does. It never happened before though - have you changed your compilation settings? (e.g., optimisation ?) D a v e
Re: SAAEmu 0.61
1. Credits? No problem. I will do the changes to let you sleep better. Ok. Thanks, 2. Get a later Word version. No. I am a poor student (That excuse used to work anyway. Doesn't actually apply now that I am no longer a student nor poor) As I wrote earlier, you can use Win98's Wordpad. I used Wordpad to write original version of that RTF file. Yes. It does. It never happened before though - have you changed your compilation settings? (e.g., optimisation ?) This is possible. Look to the size of the files (if you have older versions - you can download 0.60 and 0.61 from my web). Debug files are longer. Aley
Re: SAAEmu 0.61
Hmm, in which case why is it a .RTF file? After all, Rich Text
Format is meant to be a platform and program independant format, so
if your response is to limit the reading of the file to later
versions of Microsoft Word, would it not therefore make more sense to
simply save it in native Word .DOC format?
You should understand that I'm not an author of RTF format, so I don't
know
how and
why does it work. I just know that Internet links are present in RTF since
Microsoft
supports Internet in Windows.
Yes, by adding customised control codes to the .RTF format and thereby
making non-standard extensions to a standardised document format! (Have you
not learned about Microsoft yet?)
That mean both DOC and RTF files have these features.
Technically only for you.
You can use Wordpad to read the RTF, if your Word can't do it.
I use RTF because its functionality is 100% the same as DOC's one,
and RTF files are 5-8 times shorter than DOC ones, since DOC uses unicode.
No, you are wrong. RTF functionality is not 100% the same as DOC
functionality. No, really, REALLY. Trust me here. Show me an RTF document
that supports revision marking, for example.
True, RTF files are 5-8 times smaller than DOC ones. This is because the RTF
files have 5-8 times less crap in them. Which in turn is because the RTF
format supports 5-8 times fewer features than the DOC format.
I don't need unicode when writing English texts.
I take it, therefore, that you don't need to use the international
less-than-or-equal-to, greater-than-or-equal-to or not-equal symbols? Or any
number of a quite large bunch of useful symbols?
When I write anything which contains @, it is passed as e-mail address.
I tried this. I couldn't recreate it at all.
I tried creating documents in Word, Wordpad and Notepad and loading them
into Word, Wordpad and Notepad. And not once did any of the email addresses
I put in the document have the stupid { HYPERLINK
mailto:[EMAIL PROTECTED] }codes
That's it. I didn't know that Dave Hooper can't see this in his Word.
What can I do? I just use Word. I don't make commercial software, so I
can't
test
my RTF files on each machine and read line by line to see whether it is
okay
or not. Do you understand it? I am glad that I have Word, and I don't have
the older
versions. That's still the same - you blame me for something what is not
my
fault.
You just said yourself that you have (and use) Wordpad. Why not use wordpad
to create the .RTF file in the first place?
In fact, you could even load the .RTF file into Wordpad, select all, CUT,
new document, PASTE, and then resave, to remove any strange control codes
like { HYPERLINK }
In fact, you can just load the RTF into Wordpad and then re-save it again.
When distributing documentation, you should always make sure that whoever is
receiving your software is able to actually read that documentation!
Standard .RTF format is a safe bet. As in : what Wordpad does. Not : what
Word says it does.
D a v e
Re: SAAEmu 0.61
From: Dave Hooper [EMAIL PROTECTED] Yes, by adding customised control codes to the .RTF format and thereby making non-standard extensions to a standardised document format! (Have you not learned about Microsoft yet?) Umm... given that to my knowledge, Microsoft invented and maintains the RTF format, I think they're authorized to extend it in any way they feel fit. IMNSHO, of course. Simon
Re: SAAEmu 0.61
I'm a bit disappointed in Aley's SAAEmu 0.61.
1. Credit on the main screen (as requested!). Preferably immediately below
the line that says Z80 emulator by FMS Aley Keprt, libraries by (c) FMS
1996. If possible, credit should say SAA-1099 emulator (c)1999 Dave
Hooper
latest @ http://www.geocities.com/stripwax;. This is eighty characters.
2. Documentation (saaemu.rtf) should include my email address too. I'm
afraid my version of MSWord does not correctly render the crazy
{HYPERLINK:
mailto:[EMAIL PROTECTED] field codes - it displays Error! Bookmark
not
defined. At the very least change mine to read Dave Hooper, the author
of
SAAsound: [EMAIL PROTECTED]. Maybe change the others so they are
human-readable too?
3. Ideally, your site
(http://www.inf.upol.cz/~keprta/sam/saa//welcome.html)
should also mention a link to get the latest version of SAASound.dll. Even
an email address would do.
4. Are there bugs in saaemu 0.61? Every now-and-then it spews crazy
rubbish
all over the screen, including messages like CPU HALTed and stuck at
PC=0099h . Seems to happen especially when doing SAA32 tunes\enola and
playing and quitting and playing and quitting, a couple of times, and then
doing SAA32 tunes\tetris
I will shortly be releasing the source for saasound.dll (as soon as I'm
happy with it and it's in a readable state!)
D a v e
1. Credits? No problem. I will do the changes to let you sleep better.
2. Get a later Word version.
3. I don't know your web address.
4. Message CPU halt... is by Z80 CPU emulator. I can't say more, since I
have
never got this one. When you ask: Is there a bug? I must say: Yes, it
looks like
a bug.
Re: SAAEmu 0.61
2. Get a later Word version. Hmm, in which case why is it a .RTF file? After all, Rich Text Format is meant to be a platform and program independant format, so if your response is to limit the reading of the file to later versions of Microsoft Word, would it not therefore make more sense to simply save it in native Word .DOC format? -- James R Curry - [EMAIL PROTECTED] The Balloon Doggies DEMANDED it! The OFFICIAL James R Curry Webpage is at http://www.lhutz.demon.co.uk
RE: SAAEmu 0.61
-Original Message- From: Dave Hooper [mailto:[EMAIL PROTECTED] I'm a bit disappointed in Aley's SAAEmu 0.61. 1. Credit on the main screen (as requested!). Preferably immediately below the line that says Z80 emulator by FMS Aley Keprt, libraries by (c) FMS 1996. If possible, credit should say SAA-1099 emulator (c)1999 Dave Hooper Agreed 100%. Credit should be given where it's due I say...
Re: SAAemu 0.61
Aley is redistributing quite an old version of my SAA Sound Emulation DLL with his SAAEmu product... a much more recent version is included with Si Owen's excellent WinCoupe. I can also provide a more recent version of the DLL on request. D a v e - Original Message - From: Aley Keprt [EMAIL PROTECTED] To: Sam Users sam-users@nvg.ntnu.no Sent: Tuesday, November 16, 1999 3:51 PM Subject: SAAemu 0.61 The latest SAAemu 0.61 is available at my web site. It was there for weeks already, but there some people announced problems with downloading the file. Now it is fixed. Click to download the file directly: http://risc.upol.cz/~keprta/soft/sam/saa061.zip The package contains the player, and reusable library (.H file for C++ and two DLL files, which implement SAAsound and SAAemu) Bc. Aley [eili] Keprt - student, programmer (multimedia soft. etc.) e-mail: [EMAIL PROTECTED] *** http://get.to/aley
