This probably has nothing to do with PageStream, or problems with it, but my
question is engendered by PageStream's debug fiiles.

Sometimes (usually, maybe, but not always) those files start out with

No SOLO_ONE found!
No SB128 found!
No FM801 found!
No Envy24HT found!
No Envy24 found!
No CMI8738 found!
[keybdevLIBInit] LibInit of keyboard device
Scanning bus 'dvi'

I sort of know what a keyboard device is. I would have guessed that an SB128
would be a SoundBlaster card of the sort that should be easy to find on my
computer.

What are "SOLO_ONE" and "bus 'dvi'" etc.?

Bart

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Greetings "Bart Mathias" <mathias@hawaii.edu>
On 03/03/2010 at 02:05 you wrote concerning
[PageStreamAmigaBeta] Puzzles in DebugBufferDump.txt

Hello Bart,

BM> This probably has nothing to do with PageStream, or problems with it, but my
BM> question is engendered by PageStream's debug fiiles.

BM> Sometimes (usually, maybe, but not always) those files start out with

BM> No SOLO_ONE found!
BM> No SB128 found!
BM> No FM801 found!
BM> No Envy24HT found!
BM> No Envy24 found!
BM> No CMI8738 found!
BM> [keybdevLIBInit] LibInit of keyboard device
BM> Scanning bus 'dvi'

Interesting! The AppDebug.txt files that I've received start quite differently. Here is a small dose:

SL_AppInitA #12d
SL_AppInitA #13
SL_AppInitA #14
SL_AppInitA #15
SL_AppInitA #16 683379F8
SL_AppInitA success
PGSInit #1
PGSInit #2
PGSInit #3
PGSInit #3a
PGSInit #3b
PGSInit #4
CheckPersonalization #1CheckPersonalization #2CheckPersonalization #3CheckPersonalization #4CheckPersonalization #1InstallApp #1
InstallApp #10 - Done
PGSInit #5
PGSInit #6
PGSInit #9
PGSInit #10
makepath default buff:Help
setting APPATTR_HelpPath in:Help buffer:Help helpdir:WorkageStream5055/Help

<<snip>>

Cheers Don (Green Dragon)
--

On 03/02/2010, Ferguson, Don wrote:

> Greetings "Bart Mathias" <mathias@hawaii.edu>
> On 03/03/2010 at 02:05 you wrote concerning
> [PageStreamAmigaBeta] Puzzles in DebugBufferDump.txt
>
>
> Hello Bart,
>
>> This probably has nothing to do with PageStream, or problems with it,
>> but my question is engendered by PageStream's debug fiiles.
>
>> Sometimes (usually, maybe, but not always) those files start out with
>
>> No SOLO_ONE found!
>> No SB128 found!
>> [...]
>> Scanning bus 'dvi'
>
> Interesting! The AppDebug.txt files that I've received start quite
> differently. Here is a small dose:
>
> SL_AppInitA #12d
> [...]Help
> setting APPATTR_HelpPath in:Help buffer:Help
> helpdir:WorkageStream5055/Help

That doesn't even come *close* to answering my question, but it does evince
another puzzle.

I didn't identify the file clearly enough. My UserPrefs/AppDebug.txts look
like yours. The ones in question are invoked by a userstartup line someone
here recently suggested and may not have anything to do with PageStream at
all, since it's a regular C: command's output:

Run >NIL: CumpDebugBuffer >NIL: Spare:LastDebugBufferDump.txt CLEAR

In general the end parts of the files look a lot like GR listings, but they
may have nice little touches at the beginning like over 11,000 repeats of

Task 0x68453A90 (Shell Process) bad access @ 0xCB5A9095, pc = 0x7D949FB0, lr
= 0x7D949FD0,

As usual, I don't have a very clear idea what is going on.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Hi Bart,

On 2/03/2010, you wrote:

> This probably has nothing to do with PageStream, or problems with it,
> but my question is engendered by PageStream's debug fiiles.
>
> Sometimes (usually, maybe, but not always) those files start out with
>
> No SOLO_ONE found!
> No SB128 found!
> No FM801 found!
> No Envy24HT found!
> No Envy24 found!
> No CMI8738 found!
> [keybdevLIBInit] LibInit of keyboard device
> Scanning bus 'dvi'
>
Those are debug output from unused audio drivers in OS4.1. You obviously
have a clean installation of OS4.1 and haven't stripped out any of the
audio drivers for which you have no cards. You will get those messages
whenever the OS boots up, although they are quite harmless.

If you look in Devs:AudioModes, you will see all the drivers. You can delete
or move into Storage/Devs/AudioModes, any of the drivers for which you see
that message. I made a new drawer in that directory called "unused" and
moved them into there, but you don't have to if you don't want to.
>
cheers
tony

On 03/03/2010, Tony Wyatt wrote:

> Hi Bart,
>
> On 2/03/2010, you wrote:
>
>> This probably has nothing to do with PageStream, or problems with it,
>> but my question is engendered by PageStream's debug fiiles.
>>
>> Sometimes (usually, maybe, but not always) those files start out with
>>
>> No SOLO_ONE found!
>> No SB128 found!
>> No FM801 found!
>> No Envy24HT found!
>> No Envy24 found!
>> No CMI8738 found!
>> [keybdevLIBInit] LibInit of keyboard device
>> Scanning bus 'dvi'
>>
> Those are debug output from unused audio drivers in OS4.1. You
> obviously have a clean installation of OS4.1 and haven't stripped out
> any of the audio drivers for which you have no cards. You will get
> those messages whenever the OS boots up, although they are quite
> harmless.
>[...]

Thanks for clearing that up for me, Tony. It turns out I was confusing some
other debug files with PageStream debug files, so this was clearly (now)
the wrong place to post my query.

A puzzle and a half remain. That doesn't seem to account for "bus 'devi'" or
explain the cases when I *don't* get those messages, but those aren't
important.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Hello Bart

On 04/03/2010, you wrote:

> On 03/03/2010, Tony Wyatt wrote:
>
>> Hi Bart,
>>
>> On 2/03/2010, you wrote:
>>
>>> This probably has nothing to do with PageStream, or problems with it,
>>> but my question is engendered by PageStream's debug fiiles.
>>>
>>> Sometimes (usually, maybe, but not always) those files start out with
>>>
>>> No SOLO_ONE found!
>>> No SB128 found!
>>> No FM801 found!
>>> No Envy24HT found!
>>> No Envy24 found!
>>> No CMI8738 found!
>>> [keybdevLIBInit] LibInit of keyboard device
>>> Scanning bus 'dvi'
>>>
>> Those are debug output from unused audio drivers in OS4.1. You
>> obviously have a clean installation of OS4.1 and haven't stripped out
>> any of the audio drivers for which you have no cards. You will get
>> those messages whenever the OS boots up, although they are quite
>> harmless.
>>[...]
>
> Thanks for clearing that up for me, Tony. It turns out I was confusing
> some other debug files with PageStream debug files, so this was clearly
> (now) the wrong place to post my query.
>
> A puzzle and a half remain. That doesn't seem to account for "bus 'devi'"
> or explain the cases when I *don't* get those messages, but those aren't
> important.

Scanning bus 'dvi' is just the atiradeon.chip driver checking for a monitor
connected via a DVI cable, nothing to worry about

You will only get these during bootup so if you run pagestream again they
won't be part of that debug data.

Regards
--
<sb>Nick Clover
<sb>Corripe Cervisiam
<sb>
<sb>I never have any idea of what anyone (including myself.. scratch that,
ESPECIALLY myself) is talking about ever. I find it is safer that way. I
always have deniability should things turn serious.
<sb>

Ferguson, Don wrote:
> Greetings "Bart Mathias" <mathias@hawaii.edu>
> On 03/03/2010 at 02:05 you wrote concerning
> [PageStreamAmigaBeta] Puzzles in DebugBufferDump.txt
>
>
> Hello Bart,
>
> BM> This probably has nothing to do with PageStream, or problems with it, but my
> BM> question is engendered by PageStream's debug fiiles.
>
> BM> Sometimes (usually, maybe, but not always) those files start out with
>
> BM> No SOLO_ONE found!
> BM> No SB128 found!
> BM> No FM801 found!
> BM> No Envy24HT found!
> BM> No Envy24 found!
> BM> No CMI8738 found!
> BM> [keybdevLIBInit] LibInit of keyboard device
> BM> Scanning bus 'dvi'
>
> Interesting! The AppDebug.txt files that I've received start quite differently. Here is a small dose:
>

I believe Bart is using sashimi to save the system wide debug output. It
would include _any_ application debug output, not just PageStream's, and
this is definitely _not_ PageStream's

No idea what it is from, but very likely your OS itself!

Deron

--
Deron Kazmaier - support@pagestream.org
Grasshopper LLC Publishing -http://www.pagestream.org
PageStream DTP for Amiga, Linux, Macintosh, and Windows

On 03/03/2010, PageStream Support wrote:

> Ferguson, Don wrote:
>> Greetings "Bart Mathias" <mathias@hawaii.edu>
>> On 03/03/2010 at 02:05 you wrote concerning
>> [...]
>> BM> This probably has nothing to do with PageStream, or problems with
>> it, but my BM> question is engendered by PageStream's debug fiiles.
>>
>> BM> Sometimes (usually, maybe, but not always) those files start out
>> with
>
>> BM> No SOLO_ONE found!
>> [...]
>> BM> Scanning bus 'dvi'
>>
>> Interesting! The AppDebug.txt files that I've received start quite
>> differently. Here is a small dose:
>
>
> I believe Bart is using sashimi to save the system wide debug output.
> It would include _any_ application debug output, not just PageStream's,
> and this is definitely _not_ PageStream's
>
> No idea what it is from, but very likely your OS itself!
>
> Deron

Indeed, I reported later my discovery that those were not the result of
DEBUG/DEBUGFILE in PageStream5.prefs, but produced by the command
CumpDebugBuffer. Still, when they say things like

Crashed process: appsageStream5/PageStream5 (0x68A3CA80)

they are possibly relevant.

As a matter of fact, I still haven't figured out how to make sashimi work.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Hi Bart,

On 5/03/2010, you wrote:

> As a matter of fact, I still haven't figured out how to make sashimi
> work.
>
Firstly, Sashimi must be in your command path somewhere (you could put it in
C:, but I prefer add-ons like that in SDK:C/.

Try this line in the Shell before you run PGS:

Run >NIL: Sashimi BUFK=128

It will capture all the debug output into a file called "T:sashimi.out"

To close the file and exit, type:
sashim save
sashimi off

I have the above commands in two script files "StartSash" and "StopSash".

cheers
tony

Greetings "Tony Wyatt" <wyattaw@optushome.com.au>
On 06/03/2010 at 10:21 you wrote concerning
Re: [PageStreamAmigaBeta] Puzzles in DebugBufferDump.txt

Hi Tony,

Thanks for the advice as to how to use Sashimi, but .....

<<snip>>
TW> Firstly, Sashimi must be in your command path somewhere (you could put it in
TW> C:, but I prefer add-ons like that in SDK:C/.

TW> Try this line in the Shell before you run PGS:

TW> >NIL: Sashimi BUFK=128

TW> It will capture all the debug output into a file called "T:sashimi.out"

TW> To close the file and exit, type:
TW> sashim save
TW> sashimi off

TW> I have the above commands in two script files "StartSash" and "StopSash".

Ok, I got that, but in testing PageStream 5055, it frequently happens that PageStream freezes solid; i.e., no mouse activity, no response whatsoever. So the only way to continue is to reboot, and upon rebooting the file «T:sashimi.out» is surely lost. That's why I have used

cd «dir where sashimi resides»
«dir where sashimi resides» > RUN sashimi >«some directory on hard drive»/sashimi.txt

Did the above just before opening PageStream 5055 who quickly froze after loading a document. However, on reboot, there was a file «sashimi.txt» with lots of data in it.

Why is it a good idea to include the part «BUFK=128» ?

Cheers Don (Green Dragon)
--

On 03/06/2010, Tony Wyatt wrote:

> Hi Bart,
>
> On 5/03/2010, you wrote:
>
>> As a matter of fact, I still haven't figured out how to make sashimi
>> work.
>>
> Firstly, Sashimi must be in your command path somewhere (you could put
> it in C:, but I prefer add-ons like that in SDK:C/.
>
> Try this line in the Shell before you run PGS:
>
> Run >NIL: Sashimi BUFK=128

I will try that. I can't find anything in the documentation to suggest that
putting

Run >NIL: Apps:Sashimi/Sashimi CONSOLE RECOVER=thedump BUFK=64 NOPROMPT
ASKEXIT ASKSAVE

in user-startup shouldn't work, but it doesn't.

> It will capture all the debug output into a file called "T:sashimi.out"

I don't see how this could do any good. T: gets emptied when I reboot, which
is always necessary when PageStream kills the input devices.

> To close the file and exit, type:
> sashim save
> sashimi off

? Again, impossible with a dead keyboard.

Rereading the doc suggests that I need a path in the "RECOVER=" name. I'll
give that a try, anyway.

--
Bart Mathias
AmigaOne XE-G4 OS4.1u1

Hi Don,

On 6/03/2010, you wrote:

> Did the above just before opening PageStream 5055 who quickly froze
> after loading a document. However, on reboot, there was a file
> «sashimi.txt» with lots of data in it.
>
Good to hear.

> Why is it a good idea to include the part «BUFK=128» ?
>
Can't remember. I don't use Sashimi myself, I quoted an old script from
yonks ago in the 68K days.

These days I use only the serial port of my A1-XE or Sam, connected to my
Sam or A1-XE, where I run Term II and capture output on the other machine.
(I have two machines running)

On the odd occasion when I have used Sashimi on the A1, I've used that
script I gave you, but it sucks for the same reason as you found out. I'm
sure there ought to be a command option to open a file somewhere other than
T:.

cheers
tony

Hello Tony

On 07/03/2010, you wrote:

> Hi Don,
>
> On 6/03/2010, you wrote:
>
>> Did the above just before opening PageStream 5055 who quickly froze
>> after loading a document. However, on reboot, there was a file
>> «sashimi.txt» with lots of data in it.
>>
> Good to hear.
>
>> Why is it a good idea to include the part «BUFK=128» ?
>>
> Can't remember. I don't use Sashimi myself, I quoted an old script from
> yonks ago in the 68K days.
>
> These days I use only the serial port of my A1-XE or Sam, connected to my
> Sam or A1-XE, where I run Term II and capture output on the other
> machine. (I have two machines running)
>
> On the odd occasion when I have used Sashimi on the A1, I've used that
> script I gave you, but it sucks for the same reason as you found out. I'm
> sure there ought to be a command option to open a file somewhere other
> than T:.

Just use the simple solution of assigning T: somewhere else before running
pagestream or use a little dos script eg.

failat 20
makedir sys:t
assign t: sys:t
cd pagstream5
pagestream5

Save that as pagestream, protect +s it, even add an icon so you can start
pagestream from workbench that way...

add the sashimi start/stop commands too if you want.

Regards
--
<sb>Nick Clover
<sb>Corripe Cervisiam
<sb>
<sb>I never have any idea of what anyone (including myself.. scratch that,
ESPECIALLY myself) is talking about ever. I find it is safer that way. I
always have deniability should things turn serious.
<sb>