similar to: can't load DLL error message

Displaying 5 results from an estimated 5 matches similar to: "can't load DLL error message"

2005 Nov 20
2
Nortel Extranet Client Installer
Hi, My first post to the list so hopefully I'm not making any newbie blunders. Searched high and low for solutions to get the Nortel vpn Extranet client installer to run properly using wine. I get a ton of fixmes like these and lots of other errors, in particular ones to do with DLL32/DLL16/NETDI/SETUP16 - details follow... fixme:key:GetQueueStatus QS_xxxx flags (4000) are not handled
2006 Jun 16
1
Serial port woes
I am trying to get an app called GMWIN running. It installs and runs, but it cannot communicate via the serial ports. It is a controller for PLCs, and its purpose is to talk to PLCs via serial ports, so this is essential... Here's the error I am getting (the NIY-hEvent is repeated many times): [i386]yan@TravelSlug:~$ wine "c:/gmwin_4/gmwin" err:thunk:_loadthunk (DLL16.DLL,
2011 Nov 16
1
Difference in gnome between centos <> fedora
Hello, I've on my home PC CentOS 6 and Fedora 13 on different disks. When I log on the gnome enviroment at Fedora knows exactly which programm was started at which desktop (for example: thunderbird on desktop 1, firefox on desktop 2, nautilus on desktop 3, ..). The same procedure on Centos takes all programs on the first desktop, so I must arrange the programs on the right desktop.
2011 Nov 24
2
Applications on different deskops at startup
Hi, I've just converted my laptop to Centos 6 from Fedora ( gnome 3 made the latest fedora unusable ) and I have one problem. I have several desktops with applications running on them, mainly terminals. At login all the terminals start on desktop 1. How do I get them to start on the desktop they were running on at logoff. That's how it worked on Fedora 13/14 so it must be popssible
2012 May 08
6
registry vulnerabilities in R
Kirtland Air Force Base has denied approval for the use of R on its Windows network. Some of their objections seem a bit strange, but some appear to be legitimate. In particular, they have detected registry "vulnerabilities" which are detailed in the attachment. I know nothing about Windows registry vulnerabilities. If any of these issues are legitimate concerns,