🚀 go-pugleaf

>ISTR seeing a while back something about screen depth (= #colours)
>possibly affecting operation of the serial port during comms.

>Could this be the reason why IBrowse (and others ;) may not operate
>properly /until/ and /during/ downloads until it is switched out of
>view (and best if Workbench is displayed).

Interesting tip.

> Does the complexity of the
>transfer animation have any practical effect other than taking time?

The flashing bar in the bottom right hand corner tells you there is a transfer,
so the anim can be safely turned off.(mine is and I think it improves speed.)

Getting setpatch 40.16 off aminet helps as does increasing the ibrowse memory
cache.

A suggestion was made in the Ibrowse mailing list to increase Stack to 150000,
which apparently stops lockups. (you do this by editing the icon using 
information. (I have not tried this).

Recently there have been crashes on pages using the scrolling command.

My ibrowse is in 16 colours on a 9 meg, 68020 a500, 4 connections.

I have aslo freed up chip ram by using a program called Happyenv, also on
aminet.


vet >I use Executive and have tried this switched on and off; is it
worth >scheduling serial.device, artser.device, IBrowse etc (NOSCHEDULE and
>ABOVE settings tried).

>I have set IBrowse (via MUI's System Call Inspector) to its own 8
>colour public screen (interleaved?). This I think is the problem on my
>ECS A3000/25/FPU 2+18meg system.

>Resetting it to use Workbench (8 colours) clears all (serial/comms)
>problems, but this makes life a tad difficult if other programs are
>running there and need to be easily accessed.


>Any help, of course most gratefully received!

>--
>Jon Ward                             jpw@enterprise.net
>  Canterbury                         http://homepages.enterprise.net/jpw
>  Kent, UK                           11-Jan-97 12:33:37

Please email me a copy of any reply.

Thanks,

John

John Block                         Creative, marketing aware work which
Freelance Copywriter               talks rather than blandly bores,
                                   actively promotes your product,
International                      and aims to be the best
Welcomes Dollar and Sterling.      in your market sector.
First Virtual soon.                           johnblock@copywriter.co.uk

Hi there John Block, I believe it was you who said:

> A suggestion was made in the Ibrowse mailing list to increase Stack to
> 150000, which apparently stops lockups. (you do this by editing the icon
> using  information. (I have not tried this).

Needing a stack this large on an Amiga program is a sure sign of
something wrong.

> Recently there have been crashes on pages using the scrolling command.

> My ibrowse is in 16 colours on a 9 meg, 68020 a500, 4 connections.

A 16 colour hires screen will use a lot of Chip DMA, if it's
interlaced too then it will almost certainly intefere with serial
performance.

> I have aslo freed up chip ram by using a program called Happyenv, also on
> aminet.

This will free up some RAM (HDEnv will free up even more) but it's
fast  RAM, not Chip.

>>I have set IBrowse (via MUI's System Call Inspector) to its own 8
>>colour public screen (interleaved?). This I think is the problem on my
>>ECS A3000/25/FPU 2+18meg system.

>>Resetting it to use Workbench (8 colours) clears all (serial/comms)
>>problems, but this makes life a tad difficult if other programs are
>>running there and need to be easily accessed.

Setting IBrowse to use it's own 8 colour screen is just as effective,
it's not the number of screens that affects the serial port, just the
display requirements of the frontmost one.

> Please email me a copy of any reply.

Cc'd


Neil
--
          Neil Bothwick, Warrington, England - CU Amiga CD compiler
 Connected via Wirenet - The UK's first Amiga-only internet access provider
     Mail: info@wirenet.u-net.com   WWW: http://www.u-net.com/~wirenet/
--
 After a few years in space, even Worf started to look good...

With OS 3.1, the stack maxxes out at 65532 bytes (I tried setting it higher
for some other program and when I typed STACK by itself it was 65532 no matter
what number I put in over that amount).



-- 
...cruising down the Information Superhighway at 14,400 BPS...
          ....without a license!          Wolfram Gottfried
                                          gottfrie@acca.nmsu.edu
                                          Team AMIGA

gottfried (gottfrie@acca.nmsu.edu) wrote:
: With OS 3.1, the stack maxxes out at 65532 bytes (I tried setting it higher
: for some other program and when I typed STACK by itself it was 65532 no matter
: what number I put in over that amount).

Hmm, 3.1 here working with stacks as high as 400000 no problem (I won't
bother dicussing what needs a stack that big, since it's been covered.


Take care
-- 
--                                                           --
-                                                             -
James Friesen         |who?                lucretia@spots.ab.ca
Lucretia Enterprises  |web?    http://www.spots.ab.ca/~lucretia
---------------------------------------------------------------
-                                                             -
--                                                           --

Hi there gottfried, I believe it was you who said:
> With OS 3.1, the stack maxxes out at 65532 bytes (I tried setting it higher
> for some other program and when I typed STACK by itself it was 65532 no
> matter what number I put in over that amount).

Not here it doesn't

21.Work:> stack 123000
21.Work:> stack
Current stack size is 123000 bytes

I have set a stack as high as 1MB before now


Neil
--
          Neil Bothwick, Warrington, England - CU Amiga CD compiler
 Connected via Wirenet - The UK's first Amiga-only internet access provider
     Mail: info@wirenet.u-net.com   WWW: http://www.u-net.com/~wirenet/
--
 CAUTION: Do not install prior to installation.

gottfried (gottfrie@acca.nmsu.edu) wrote:
> With OS 3.1, the stack maxxes out at 65532 bytes (I tried setting it higher
> for some other program and when I typed STACK by itself it was 65532 no matter
> what number I put in over that amount).

Not here

16\5\ $ stack
Current stack size is 65536 bytes
16\0\ $ stack 100000
16\0\ $ stack
Current stack size is 100000 bytes

16\10\ $ version
Kickstart 40.68, Workbench 40.42 


-- 
<URL:http://www.pierrot.co.uk/>                                     Team AMIGA
Life is like an onion: you peel off layer after layer, then you find
there is nothing in it.

Hello,

Neil Bothwick wrote:

> > My ibrowse is in 16 colours on a 9 meg, 68020 a500, 4 connections.
> 
> A 16 colour hires screen will use a lot of Chip DMA, if it's
> interlaced too then it will almost certainly intefere with serial
> performance.

I am using ibrowse on a 64 colour DBLPAL screen, 4MB 68030 A1200, with 8
connections
without any problems, exept with realy realy graphic intensive pages,
but decreasing
the number of connections will probebly fix that too since the lockups
only happen when
all connections is used at the same time.

I have moved the VBR, SSP and Exec to fast ram and ONLY scheduled the
main Ibrowse task, the Ibrowse_Network tasks
is left unscheduled (Executive v2), otherwise image loading slows down
alot.

---
Mvh Hans Olsen

EMail: pt96hol@student.hk-r.se
Web: www.rby.hk-r.se/~pt96hol
IRC: UncleRed

Phasers don't kill people...Unless you set them too high.