I’ve tried 4 different versions of Linux (Mint13 Cinnamon & Mate, Mandriva and Ubuntu) and decided that Mint Cinnamon is the one I prefer. Have also tried 3 different ‘virtual’ disks to run my Win applications (KVM, VB and Crossover) and prefer Crossover - yeah I know it’s not free like most Linux apps, but I think it’s most suited to my needs.
What I can’t do is to get any of the ‘virtual’ apps to do is recognize my parallel port, where my dongle resides. I think this is more likely to be down to Linux than the ‘virtual’ apps, so my question is: -
Is there an equivalent to the WinXP “add an LPR port”. The Windows help file on the subject includes the words “To add the LPR port, you need to install the optional networking component, Print Services for Unix.” (WinXP’s bold characters). Which makes me think that there is probably a Linux command to enable one to do this.
I would say that it is more the case that it does no know what to do with the Zuken Cadstar MSDOS dongle. http://linuxforums.org.uk/index.php?topic=10541.msg79144#msg79144
Did you not needed to install the drivers in Windows to allow accessing it? You would need to do the same in Linux too.
If you have the drivers then it might be worth to try to install them in Crossover, failing that you can always ask Zuken for the Linux drivers.
We’ve probably got so many drives because Crossover has logged and remembered all my internal HDDs(c: thru g:).
y: (marked by crossover as “/home.tony”), and z (marked as “/”) are partitions I believe to be created by Crossover (?).
Although a load of HDDs are listed I cannot access any of them from within any program (Cadstar or any of the Office suite) running under Crossover except for c: (marked by Crossover as “drive_c”) which has a limited amount of sub-directories (“Program Files”, “Users” and “Windows”) and is definitely not my XP64 C: drive.
I’m not sure whether or not the lpt reports above indicate that Linux is ‘seeing’ the parallel port as, when I check software key details in the Cadstar [help]/[about] it comes up blank, so I can only assume that even if Linux is ‘seeing’ it, Crossover isn’t… The first step in Cadstar installation is to install the Sentinel driver, which normally allows Cadstar to talk to the dongle. Not with my current setup though as it comes up with “…operate in unlicensed mode…” message.
Once I can get this parallel port business sorted I have to get access to my other drives, but that’s Crossover’s problem, which they reckon I ought to be able to sort. I’m now going to have a go at the instructions they sent for this and will let you know, out of interest only, how it goes.
If I download the appropriate Sentinel Linux driver it comes down in an ".rpm" format. How do I install it?
You cannot install .rpm files as your system uses .deb however there is a tool called Alien,
which can convert RPM files to DEB files.
Install that from your repo:
sudo apt-get update
sudo apt-get install alien
To install a .rpm file, you need to convert it to .deb. Place your RPM file in your ‘Home’ folder,
otherwise you will have to CD into the directory of the .rpm file then covert it:
a) If you’re going to be running your app in WINE/Crossover I don’t think you want a Linux driver … I think you need the Windows one.
and
b) Those drivers are VERY old, and not for current kernels … they DO include the source code, but it won’t compile for current kernels
I would have thought that, but when I queried with the Crossover people the need for security I was told that additional security would not be necessary because although: -
"That’s true of VirtualBox and any VM because you’re actually running the windows OS, which means you’re susceptible to windows viruses. This is not the case with Crossover or Wine. Windows viruses need a windows OS ‘host body’ to latch onto in order to function, and if you’re only running Crossover/Wine you don’t have the windows OS, or anything that looks like it from the virus’ perspective. "
Which would seem to indicate to me that a Linux driver would be more appropriate. What do you reckon?
and
b) Those drivers are VERY old, and not for current kernels .. they DO include the source code, but it won't compile for current kernels
Yes, I guess you must be right there, because even though they may be described as for “32bit and X64” by the time you’ve unpacked the ‘zip’ or ‘rar’ file, and converted the ‘rpm’ to ‘deb’ if necessary, the end result is a file containing the ‘i386’ in its title.
WINE is a Windows environment, or at least tries to be as close as possible with open source backward engineered libraries (or actual Windows libs if you install them) … if it can run a Windows executable, why wouldn’t it be able to run a malicious executable ?
Windows executables are susceptible to viruses … full stop … doesn’t matter how or on what they are run … the only thing in question is how easily they could spread, particularly to the host OS (Linux).
It’s less likely (though not impossible) that the host Linux OS could become infected (if somebody wrote malicious code designed to do infect Linux through WINE) … but anything in the WINE (.wine) directory is open for infection.
Which would seem to indicate to me that a Linux driver would be more appropriate. What do you reckon?
It’s a Windows application running in WINE, from what I gather parallel ports can be configured in WINE as direct passthrough … so I’d expect your application running in what it considers to be Windows to look for the dongle “in Widows”.
I would expect a Linux driver to make the dongle work (be available to) in Linux … I wouldn’t expect a Windows application to be able to make calls to the “Linux” driver.
My guess is you’d need the Windows driver also working in WINE, so the Windows application would be talking to a Windows driver … which is talking directly to the dongle via parallel port passthrough.
But that’s just the way I see it, and I could be wrong.
I still think this would be easier in a VM.
It may not be possible at all, in either a VM or WINE … but if it will work and I had to bet, I’d put my money on finding a way to pass the parallel port to a VM
