[Coco] pf for epson for drivewire

[Gene Heskett]

On Monday 01 April 2013 13:44:51 Aaron Wolfe did opine:

> On Mon, Apr 1, 2013 at 1:03 PM, Gene Heskett <gheskett at wdtv.com> wrote:
> > On Monday 01 April 2013 11:42:18 Aaron Wolfe did opine:
> >> On Mon, Apr 1, 2013 at 11:20 AM, Gene Heskett <gheskett at wdtv.com> 
wrote:
> >> > I just checked and Aaron, whats the biggest file I can us as a
> >> > drivewire disk?  The one I have been using as a scratchpad is now
> >> > over 10 megs.
> >> 
> >> DW uses a 24 bit LSN, so 4 GB is max device size.  Max
> >> filesystem/volume size will depend on the CoCo side software.  I
> >> believe NitrOS9 is fine with 4 GB.
> > 
> > In other words, NP unless linux has a problem with a 4+Gb file.  :)
> > 
> > Thanks Aaron.  I just rebooted this machine, and haven't restarted dw
> > yet, but I switched to the new package, so it should Just Work(TM) it
> > says here.
> > 
> > But when do we fix the coco's client so that this machine can be
> > rebooted without crashing the coco? It only works if I have it
> > running here, and go reset the coco3.  So I'll do that next, brb.
> > 
> > Murphy has arisen from the dead, I thought I'd outlived that jerk.
> > 
> > Because even as root, no runnee. Says unk option -XstartOnFirstThread.
> > I had moved all my .xml files to the new version from 4.3.1g.
> > 
> > Humm -XstartOnFirstThread does not grep in the *.xml's  Took that out
> > of my starter command script.  Now it doesn't load the default disks.
> >  Why not?
> 
> -XstartOnFirstThread is a Java VM option that is only needed (and only
> valid) on Macs.
> 
> There are 3 OS specific scipts/launchers:
> 
> DW4UI.exe is for Windows
> DW4UI.command is for Macs (and contains the -XstartOnFirstThread option)
> DW4UI.sh is for Linux/*nix
> 
> You can also just double click on DW4UI.jar on many systems, or enter
> the command:
> 
> java -jar DW4UI.jar
> 
> > Loaded them ok by hand, now go reboot the coco3.  No connect.  The
> > coco probes them by attempted cd's before opening a shell window in
> > its startup, and I see those tx blinks on the usb interface, but no
> > response from this machine, so obviously my copying the xml files
> > over didn't work.  OPen the editor, serial port is COM14???  S/B
> > /dev/ttyUSB0, tried both ttyUSB's, doesn't work.
> > 
> > Opening the load or save file buttons also see no .xml files.  I'll
> > switch the directory link back to the 4.3.1g tree & retest.  And had
> > to nuke that same option in that DW4UI.command java invocation file
> > too.  And it still did not load the default disk, had to do it by
> > hand.  So, now, go reboot coco3 again.  Nope, no server.  Open config
> > editor & its AFU again, from the old, did work just fine, *.xml
> > files.
> > 
> > Fooled around for another half an hour and finally got it to start
> > with the selected disk images loaded.  And the config editor says the
> > correct usb port is being used, which turned out to be ttyUSB1.  But
> > still no heartbeat from the coco.  The USB circuit is good, I just
> > printed a test page from cups to the printer on top of the coco's
> > desk, all the same wire to the final hub down there.
> > 
> > I'm fresh out of ideas Aaron, what else do I check?  It was working,
> > and had been since the last reboot 2 weeks ago, I had even gotten a
> > dir from /x1 on it 2 hours ago.
> 
> Do not use the DW4UI.command file.  It is for Macs.  Use the DW4UI.sh
> file or just type:
> 
> java -jar DW4UI.jar
> 
> (or fire that command off any way you'd like)
> 
> Try a "killall java" at the linux prompt to make sure we don't have
> orphaned processes hanging around.

Its more complicated than that, my printer "wizard" needs to be killed, 
along with whatever instance of inotifywait is watching the caching dir 
used for printable files.
 
> Then open DW and use the Simple Config wizard from the Config menu.
> 
> Does it find your serial port?  If not, we may have a permissions
> issue.  If so, complete the simple wizard and see if things start
> working.

I've long since found I have to run it from a root shell, so thats what I 
am doing.  I just edited my dwstart file to use the .sh version, quit, 
cleaned up and restarted it yet again.  Now go reboot the coco for about 
the 15th time.

Still dead.  The printer on the same usb cable works.  So I just went thru 
the simple wizard, letting it enable the /midi even though I don't have the 
/midi in my bootfile and its working now I think.

Yup, just fine.  What the diff was I haven't a clue.

But I need to go back thru it again as I just found the reason in the 
defaults it showed me, why my 'cocoprints' caching directory is always 
moving around, its not an absolute path!  My bad I expect.  However, I had 
to cancel as it only looks for available USB ports and its using USB1, and 
can't either take the current port, or let me add it manually.  But I can 
edit the .xml to fix that now that I have found the problem.  Done and 
written both to the config.xml file and to the server.

Now, if we could get a buildable repo besides mine back in business, I 
might see if I could fix the coco driver so it doesn't kill the coco when I 
reboot this machine.

Looks like I am back in business for a while.

Do carry on, sheer unmitigated panic session is over. :)

Thanks too Aaron.

> -Aaron
> 
> > Here is my DW4UI.command file:
> > #!/bin/sh
> > cd ${0%/*}
> > 
> > java -XX:+UseConcMarkSweepGC -jar DW4UI.jar --backup --nomidi &
> > 
> > Your turn?
> > 
> > Cheers, Gene

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!
My views 
<http://www.armchairpatriot.com/What%20Has%20America%20Become.shtml>
Travel important today;  Internal Revenue men arrive tomorrow.
I was taught to respect my elders, but its getting 
harder and harder to find any...