Results 1 to 2 of 2
penquin bro sis? so wine has been good with with clean memory clean up when exiting apps even better than xp commercial version. question(s): 1)how do i get native .msc ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-19-2011 #1
- Join Date
- May 2011
wine: getting .msc and windows device manager plug n play to work?
- 07-19-2011 #2
- Join Date
- Apr 2009
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
You won't get tools like disc manager, device manager, etc to work with Wine. Ditto Windows device drivers. Wine uses the Linux device services under the covers. As for IrD (infrared) devices, you will need the appropriate Linux device drivers for them, but you also need to build IrDA support into the kernel, which is not usually done by default. It is an option you can configure into the kernel build, but then you will need to build/install that kernel into your system. Here is some information from the 2.6.32 kernel configuration tool:
IrDA (infrared) subsystem support (IRDA)
Say Y here if you want to build support for the IrDA (TM) protocols.
The Infrared Data Associations (tm) specifies standards for wireless
infrared communication and is supported by most laptops and PDA's.
To use Linux support for the IrDA (tm) protocols, you will also need
some user-space utilities like irattach. For more information, see
the file <file: Documentation/networking/irda.txt>. You also want to
read the IR-HOWTO, available at
If you want to exchange bits of data (vCal, vCard) with a PDA, you
will need to install some OBEX application, such as OpenObex :
To compile this support as a module, choose M here: the module will
be called irda.
Symbol: IRDA [=n]
Prompt: IrDA (infrared) subsystem support
Defined at net/irda/Kconfig:5
Depends on: NET [=y] && !S390 [=S390]
-> Networking support (NET [=y])
Selects: CRC_CCITT [=m]Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!