[Coco] DW4 problems

Sun Oct 14 02:06:00 EDT 2012

Hi Aaron,
I tried your suggestion:

> java -Xmx1024 -jar DW4UI.jar

but I get an error:
Error occurred during initialization of VM
Too small initial heap

I am running Windows XP SP3. Not sure which version of Java, but I keep it 
updated whenever it requests that.

Regards, Bob Devries
Dalby, QLD, Australia

----- Original Message ----- 
From: "Aaron Wolfe" <aawolfe at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, October 13, 2012 8:43 PM
Subject: Re: [Coco] DW4 problems

> The largest OS9 image I use is 40MB in size, so copying monster RBF
> filesystems is not well tested.  There may be unexpected issues.
>
> Copying large drives may require an unusually large amount of RAM
> (approx equal to the size of the drive you are copying + 8MB) if DW is
> in caching mode.
> By default the Java VM will have a relatively small limit, depending
> on your OS anywhere from 32MB to 256MB.  That's totally fine for
> normal use, but when changing every sector on a drive while the server
> is caching changed sectors, you may run out.
>
> You can allocate any amount of ram to DW using the command line.  The
> command will look like:
>
> java -Xmx1024 -jar DW4UI.jar
>
> (assuming you are currently in the directory where DW4UI.jar lives,
> which is a good idea)
>
> That example gives DW up to 1024MB ram.  This does not mean DW will
> actually request or use 1024MB, just means that if it does it can have
> it.
>
> I am not certain, but this may solve both issues.
> -Aaron
>
>
> On Sat, Oct 13, 2012 at 6:32 AM, Gene Heskett <gheskett at wdtv.com> wrote:
>> On Saturday 13 October 2012 05:19:09 Bob Devries did opine:
>>
>>> I might add that I tried using BACKUP to clone the SCSI HD to the DW
>>> disk image, but that quits at the first error 245.
>>>
>> That is about the same as I got, trying to do a sector by sector copy 
>> using
>> my basic09 version of the linux dd, it fell over at some random point, 67
>> megs was as far as I got in quite a few tries, and that image was not
>> recognized as an os9 formatted image by dw at any time in those attempts.
>>
>> So, since linux never really wrote that 67 megs, reporting that file to 
>> be
>> only 25 bytes long, I nuked, touched a new one and chowned it to me.  And
>> now I'll try to format it.  I used dmode to make it match the hd I want 
>> to
>> back up.
>>
>> If format screws up my /dd like it did the last time I am going to one
>> unhappy camper.  It did report similar characteristics, but I killed it
>> after about 30 seconds as the gui said that the vdisk mounted on /x1 was
>> not being accessed for anything.  Now I'm dchecking /dd and when thats 
>> done
>> I'll do /dh.  If those come back intact, I'll repeat the experiment but
>> wait for it to ask me for a disk name.  Maybe format, on a hard drive, 
>> only
>> writes LSN0 after the disk name? question.  I do not know.
>>
>> On the previous attempt to format /s1, it was not until it had started 
>> the
>> surface verify that I discovered it was working on /dd=/s0, its access 
>> led
>> was blinking like crazy and I was 10 days recovering from that, with some
>> stuff lost forever!  It totally ignored the fact that a dmode /s1 said
>> drv=01, while a dmode /dd said drv=00.
>>
>> And now I can't run dcheck, error 237-ram full.  And smap says I only 
>> have
>> 14 pages, 3kb free.  In 2 pieces.  telnet>quit is an invalid command.  I
>> hope to hell I can reboot. Whew, did, now 19 pages & 4kb according to 
>> smap.
>> And dcheck seems to be running this time.
>>
>> Later.  When I know more...
>>
>>
>>
>>
>>
>>>   ----- Original Message -----
>>>   From: Bob Devries
>>>   To: CoCoList for Color Computer Enthusiasts
>>>   Sent: Saturday, October 13, 2012 5:53 PM
>>>   Subject: DW4 problems
>>>
>>>
>>>   I seem to be getting a lot of time outs using DW4, which cause ERROR
>>> 245 on the coco end. Here's some lines from the log:
>>>
>>>   Sat Oct 13 2012 17:36:09.250  WARN   DWProtocolHandler   dwproto-0-10
>>>       Timed out reading from CoCo in OP_WRITE Sat Oct 13 2012
>>> 17:36:09.250  WARN   DWProtocolHandler   dwproto-0-10        OP_WRITE
>>> took 235ms.  Server loaded or low on ram?
>>>
>>>   DW4 is being run on an Intel P4 2.8GHz with 2GB ram. Besides the usual
>>> clutter running in a windows background (AVG etc) the only application
>>> running is Outlook Express, set to grab emails every 10 mins.
>>>
>>>   The connection is like this:
>>>
>>>   Coco <--> ATEN USB dongle <--> 8-port powered USB hub <--> USB2 Port
>>> on PC.
>>>
>>>   The CRC of DW is $5136C3
>>>
>>>   Regards, Bob Devries
>>>   Dalby, QLD, Australia
>>>
>>>   PS: I sent a more extended bug report via the DW4 UI to wherever that
>>> ends up.
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>> Cheers, Gene
>> --
>> "There are four boxes to be used in defense of liberty:
>>  soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author)
>> My web page: <http://coyoteden.dyndns-free.com:85/gene> is up!
>> Madness takes its toll.
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco 