[Coco] DriveWire 4 seg fault under Linux Mint...

[Bill Pierce]

I agree with Aaron, I use the "vport sniffer" version in my software developement and it has TONS of bugs..... but is still the one most useful thing that has been added to dw4... when it works LOL
For instance, In developing MShell, which will read (and write) files to the PC server. Having only Windows, I've been building the routines to work with Windows file systems from the Coco. I was just about to release it when I decided to try it on Linux to make sure it read the file system correctly... It was a big "NO GO".
The really strange thing is that it actually reads the Linux file directory, saves it to a temp file on the Coco, closes dw4 port, closes the temp file, then crashes hard. The sniffer shows all data was sent and received by dw4, my temp file on the vhd shows the Coco received and saved the dir list. But it crashes? It ONLY does this under Linux. In Windows, I can transfer files from PC to Coco and Coco to PC all day with no crash.
What I want to know, is how Linux/DW4 is crashing my Coco after all communication has ended?
I'm still going through things to see if there's a bug, but I would think it would've shown in Windows transfers as well. It seems to be a Linux thing.
The sniffer has been priceless in tracing down transfer problems and I couldn't live without it. I'm going to try a couple of older versions of dw4 in Linux to see if it makes a difference. I have currently tried 4.3.4e & 4.3.3p. This is only a problem when I try to read a Linux directory.

 

 


Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 

 

-----Original Message-----
From: Aaron Wolfe <aawolfe at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Nov 11, 2014 10:20 am
Subject: Re: [Coco] DriveWire 4 seg fault under Linux Mint...


Hi,

The sniffer is unfinished and very buggy in 4.3.4 :(  I hope you will
understand that all bets are off in that version.

Eventually when/if it is released yes there will be a sniffer.  In the
meantime, you can log all bytes to the log file with options in the
config.xml, but this is only useful in certain situations.
On Nov 11, 2014 10:15 AM, "Jens" <CoCoList at jensdiemer.de> wrote:

> Am 11.11.2014 um 15:52 schrieb Tormod Volden:
>
>> Jens, you must have something mounted in slot 0. This was written on
>> the Dragon forums - half of the thread is about this :)
>>
>> Otherwise a DriveWire4 handler will crash.
>>
>
> Hm. You mean:
> http://archive.worldofdragon.org/phpBB3/viewtopic.php?f=5&
> t=4964&start=30#p12101
>
> ???
>
> That's only for HDB-DOS or NitrOS-9 needed?!?
>
>
>
> Under Windows with Drivewire 4.3.30 everything works. Without to mount any
> drive...
>
> I just copy the dwload-demo-files into the root and setup the COM... Then
> "AUTOLOAD.DWL" will be loaded and i see the menu on the Dragon...
>
>
> Now i cleanup my linxu installation... Take the running windows copy and
> edit the config.xml (change COM3 to /dev/ttyUSB0)
>
> And no it works, too.
>
> Strange...
>
>
>
> @Aaron: I saw in 4.3.4e the file "/plugins/Sniffer.jar"... That's very
> interesting, because i would like to sniff the serial communication...
>
> It is possible to use this in 4.3.30 ?!?
>
> Or is there a other easy way to sniff the serial data?
>
>
>
> --
>
>
> Mfg.
>
> Jens Diemer
>
>
> ----
> http://www.jensdiemer.de
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco