[SD-User] sdi and wine

[Nick G4IRX]

According to the Wine user guide there are three different ways of
running a Windows console mode application:
http://www.winehq.org/site/docs/wineusr-guide/cui-programs

Just to add if you want to run any Windows apps on Linux or Mac OSX then
Sun's VirtualBox emulator is free for personal use and performs
extremely well. For console apps such as SD it's best to use something
from the NT family so avoid 95/98/ME. If you don't have a copy of
Windows then you can get evaluation copies that will run for six months
by registering with MS as a developer - I have obtained Windows 7 RC and
2003 Server by that route and they run quite happily on MacOS 10.5 and
Ubuntu 9.04. 

One other advantage of the emulator is that it is possible to map all
your serial ports into the range that are supported in SD. Disadvantage
is that there is no parallel port so you will have to use Winkey.

73
Nick G4IRX 

-- 
Nick G4IRX

----- Original message -----
From: "Ian Greenshields" <ian.greenshields at gmail.com>
To: "sduser" <sd-user at contesting.com>
Date: Mon, 29 Jun 2009 10:03:15 +0100
Subject: Re: [SD-User] sdi and wine

I have also seen this effect on some computers / distributions. I have
no
problem on the Asus eeePC (701) running the stock Xandros and Wine
0.9.58 -
SD runs fine & is fast enough for normal CW contest operation. I have
another PC at home which runs DSL (a stripped Debian), also with Wine
0.9.58
and it is very slow, almost to the point of being unusable.

I don't know what the solution is, other than try a different distro.
All
recent versions of Wine (last 2 years or so) seem to run SD the same & a
faster processor doesn't seem to noticeably improve things either.

The only real solution is to compile SD for Linux - if PowerBasic CC 
had a
Linux compiler......

73 Ian G4FSU


2009/6/28 Anders Eidenvall <anders at eidenvall.se>

> Thanks for the help and your interest.
>
> I have tried your suggestion and a normal terminal window is working OK
> when
> SDI is running in wine. Nothing unusual such as slow operation can be seen.
>
> What I can see is that SDI is consuming a lot of CU cycles during this
> time.
> As an example:
>
> If I enter a call in the call field and then hits backspace a few times to
> get rid of the call, SDI is consuming 100% of my 2.3GHz CPU for at least 5
> seconds. I can also see that when SDI is just idling in wine, bursts of
> 100%
> CPU-cycles are consumed for about one second every 5 seconds. They
> disappear
> when I close wine.
>
> About a possible regression bug, I have tried this with both the stable
> wine
> release and with the latest development release with the same result.
>
> Anders Eidenvall
>
>
> 2009/6/28 Bill Gearhiser <thegear at aol.com>
>
> >  I've used SD and wine on Fedora and definitely did not see that problem.
> > It was not very fast, but it didn't have any pathological behaviors like
> you
> > mention.
> >
> > You might want to try this: while SD is running inside wine, open a
> > terminal and issue some commands (ls, pwd, ...) to see whether they
> > misbehave in the same way. If so, something is stealing CPU cycles, and
> we
> > can investigate that (ps -auxw, on some Linux/Unix/Solaris systems). If
> not,
> > then wine is the culprit. It could be a "regression bug", in which a fix
> for
> > something introduces a new problem. I don't know what version of wine I
> was
> > using, and that system doesn't exist any more.
> >
> >  Bill Gearhiser
> >
> >
> >
> >  -----Original Message-----
> > From: Anders Eidenvall <anders at eidenvall.se>
> > To: sd-user at contesting.com
> > Sent: Sun, Jun 28, 2009 5:00 pm
> > Subject: [SD-User] sdi and wine
> >
> >  Hello
> >
> > I am preparing for the summer IOTA-contest and this year I planned to get
> >
> > rid of the paper logging so I am trying to use SDI under wine on ubuntu
> 8.10
> >
> > and 9.04 under wine.
> >
> >
> > Things seems to be working but the reaction to typing is v e r y slow. It
> >
> > takes about 3 seconds from the call entry untill the cursor stops at the
> >
> > serial number entry field. After the ENTER to log the QSO it takes nearly
> 5
> >
> > seconds until the QSO shows up in the QSO list and an additional 3
> seconds
> >
> > until the cursor is located in the call entry field again. During all the
> >
> > time delays, the cursor can be seen jumping around.
> >
> >
> > I have tried this both on a eeePC 900 MHz and on my stationary Acer. Both
> >
> > computers react the same. I have also tried both the stable wine release
> >
> > 1.0.1... and the latest development release with the same behavour.
> >
> >
> > Anyone seen this before or know how to correct it.
> >
> >
> > 73 de SM5EFX, Anders Eidenvall, SF2X on EU135
> >
> > _______________________________________________
> >
> > SD-User mailing list
> > SD-User at contesting.com
> > http://lists.contesting.com/mailman/listinfo/sd-user
> >
> >
> > ------------------------------
> > *A Good Credit Score is 700 or Above. See yours in just 2 easy steps!<
> http://pr.atwola.com/promoclk/100126575x1221323006x1201367222/aol?redir=http://www.freecreditreport.com/pm/default.aspx?sc=668072%26hmpgID=62%26bcd=JunestepsfooterNO62
> >
> > *
> >
> _______________________________________________
> SD-User mailing list
> SD-User at contesting.com
> http://lists.contesting.com/mailman/listinfo/sd-user
>
_______________________________________________
SD-User mailing list
SD-User at contesting.com
http://lists.contesting.com/mailman/listinfo/sd-user