Hi All, I have just moved over to PCLINUXOS2007 from Windows XP and have found it to be a great Distro. The only software I'm keeping Windows XP for is a high end Cad/Cam Package called AlphacamV2004 from Licom Systems which I use for work and home. I've installed Alphacam with Wine version 0.9.58 and the Advanced Lathe module seems to work fine with no bugs so far, the Advanced Mill 3axis and 5 axis modules work ok but with Quick Shading and Advanced Shading of 3D models the active drawing screen goes blank but is restored when I go back to Wire Mesh surfaces, also when I select a tool from the tool select pop up screen to do a tool path the programs shut down with no error messages. Hoping someone might have an idea what is causing the shutdown of the program and no shading/rendering of the solid model. There are a lot of Alphacam specific dll's in the AlphaV5 directory with only 2 identical with the dll's in Wine\System32 MSVCRT.DLL and MFC42.DLL. Have put them both as native but with no success. System is an... Intel D875PBZ M/B, Intel P4 875 Prescott CPU, 2Gig Ram, ATI Radeon 9600SE Graphics Card. 400Gig WD SATA HD. PCLINUXOS2007, Wine 0.9.58 I'm fairly new to Linux and still trying to get my head around it but find it much better than MS Windows. Thanks in advance for your help.
FrankN <wineforum-user at winehq.org> wrote:> I've installed Alphacam with Wine version 0.9.58 and the > Advanced Lathe module seems to work fine with no bugs so far, > the Advanced Mill 3axis and 5 axis modules work ok > but with Quick Shading and Advanced Shading of 3D models > the active drawing screen goes blank but is restored when > I go back to Wire Mesh surfaces, > also when I select a tool from the tool select pop up screen > to do a tool path the programs shut down with no error messages.To diagnose crashes like that, we usually ask for a log. Try running the app like this: WINEDEBUG=+seh,+relay foo.exe > log.txt 2>&1 and then get the crash to happen as quickly as possible (to keep the log short). Then compress the log and upload it somewhere for us to look at. It would be a lot easier if we had a copy of the app to try ourselves, but looking at licom.com, it seems they don't have demos. - Dan
Dan Kegel wrote:> > To diagnose crashes like that, we usually ask for a log. > Try running the app like this: > WINEDEBUG=+seh,+relay foo.exe > log.txt 2>&1 > and then get the crash to happen as quickly as possible > (to keep the log short). Then compress the log and upload > it somewhere for us to look at. > > It would be a lot easier if we had a copy of the app to try ourselves, > but looking at licom.com, it seems they don't have demos. > - DanThanks for your prompt reply Dan, Could not get the WINEDEBUG=+seh,+relay /home......ALPHAV5/AM3AXAPS.EXE > log.txt 2>&1 to work, seems WINEDEBUG is not part of the PCLINUXOS wine package. Found a log.txt in the ALPHAV5 directory which read... wine: could not load L"C:\\windows\\system32\\WINEDEBUG=+seh,+relay.exe": Module not found err:winedevice:ServiceMain driver L"DK12DRV" failed to load err:winedevice:ServiceMain driver L"hardlock" failed to load err:winedevice:ServiceMain driver L"Haspnt" failed to load I could send you a CD with the App and install Instructions for Windows XP If that would be of any help. Regards, Frank
On Tue, Apr 29, 2008 at 4:11 AM, FrankN <wineforum-user at winehq.org> wrote:> Could not get the WINEDEBUG=+seh,+relay /home......ALPHAV5/AM3AXAPS.EXE > log.txt 2>&1 > to work, seems WINEDEBUG is not part of the PCLINUXOS wine package.WINEDEBUG is just an environment variable, you still have to use wine. I had a typo in my example, should have been WINEDEBUG=+seh,+relay wine foo.exe > log.txt 2>&1
FrankN wrote:> err:winedevice:ServiceMain driver L"DK12DRV" failed to load > err:winedevice:ServiceMain driver L"hardlock" failed to load > err:winedevice:ServiceMain driver L"Haspnt" failed to loadThose are "USB dongle" drivers - they won't work on Wine. I'm assuming that they came with your program. If that's the case - it will not work on Wine as-is.