I finally gave in and installed the beta on a fresh boot partition
using Update 4. I did an MD5sum check on the downloads and they are
OK. The result leaves me totally at a loss.

On first run after the install, a requester came up saying that there
was a conflict in the USB stack ('There are unsolvable problems with
the UHCI Controller') and did I want to stop the controller. I said
'close it', but the same requester kept coming up. I looked for the
USB stack initiation in the startup scripts and found none.

I rebooted and used USB stop before running Pagestream. I was able to
register it. Once registered, the filters, etc. load and I get a GR.
Workbench freezes, but GR reports a DSI crash, Instruction Pointer
0x01423110 in Module kernel. On rebooting using the power switch, when
running it after a USB stop I get the message about the filters, etc.
loading and then I get the Toolbar (with the object and text
selectors) window and another window with a single tool icon
comprising a ghosted box. Neither window makes menu items available.
Placing a window over the Toolbar and bringing the Toolbar to the
front deletes the tool icon images so they are not being redrawn.

Just running Pagestream drops the free memory from 82% to 73% and then
it slowly drops down to 39%. This corresponds to 199 MB. I wonder if
this also corresponds to the memory required for Kickstart modules and
Workbench. Trying to open Workbench drawers to run another program
gives the warning in the screen title bar 'This drawer cannot be
opened' or the program just does not run. Some programs go straight to
'insufficient memory'. It sounds as though Pagestream is vacuuming up
all the free memory until Workbench runs out of space to do anything
else.

Running without using USBStop brings one instance of the UHCI
controller message, but stopping the controller prevents further
messages. Renaming CSets does not change anything.

Obviously the problem is...

Nope. It beats me. I can't even guess! I have found the same thing
after two complete deletions and reinstalls of the program directory.
I would be interested to see if anyone else can reproduce the memory
behaviour. The memory can be set to display in the Workbench screen
title bar by setting the options in the Workbench prefs.

Regards
Roy Leith

On 2006-02-24, royleith wrote:

[...]
> I looked for the USB stack initiation in the startup scripts and found
> none.

My installation is not a clean one, so I looked at the CD and line 33 in
AmigaOS40_CD:System/S/Startup-Sequence looks like this:

c:usbctrl start

Probably you have the same startup-sequence (version 51.2).

--
//Jonas_H
/o\
// \\ The ASCII
\\ // Ribbon Campaign
\V/ Against HTML
/A\ eMail!
// \\

--- In PageStreamAmigaBeta@yahoogroups.com, Jonas Hofmann <jonas@...> wrote:

>
> My installation is not a clean one, so I looked at the CD and line 33 in
> AmigaOS40_CD:System/S/Startup-Sequence looks like this:
>
> c:usbctrl start
>
> Probably you have the same startup-sequence (version 51.2).

You are quite right, of course. I must have been feeling particularly stressed when I was looking for it. I'll comment it out when I return to beta testing.

Regards
Roy Leith