Hello!
I'm trying to get an old program working, but I keep getting the error "Runtime error '70': permission denied" and a crash.
The program is LpStudio (from 2001) which is used when recording audio books, and it runs best in windows xp, but using a virtual machine for this (which is what I usually do) comes with its own set of problems, so I've been trying to get it to work using WINE instead. I've installed it in a 32-bit prefix.
LpStudio records what I narrate and automatically indexes the sound down to sentences. Sometimes I need to rearrange those sentences and in the programs interface I should be able to move sounds around by marking and then cutting and pasting. Cutting and copying works, but pasting the audio causes the crash.
I've tried finding leads in the console output and it shows a lot of errors of the type "0024:warn:file:CreateFileW Unable to create file" with references to a file in the working directory. The same errors can be found in the attached logfile (output of WINEDEBUG=warn+file,+module,+seh wine lpStudioPro.exe &>log).
The working folder is owned by my user (john) and permissions look right: "drwxrwxr-x 4 john john" is the output of ls -l. At first it was located in ~/Documents and that folder was symlinked to ~/.wine/drive_c/users/john/Documents (from memory, might be an error in there), and I've also tried removing that folder from my ~/.wine/drive_c/users/john folder and creating a new, not symlinked, Documents folder there (after disabling it in winecfg), but I get the same error when working from that new, native, folder.
To get the program installed and running I've used winetricks msdxmocx mfc40, and installed wine-gecko-2.47.4-x86.msi.
All help is greatly appreciated!
Runtime error 70
Runtime error 70
- Attachments
-
- log.bz2
- (136.36 KiB) Downloaded 185 times
-
- Level 4
- Posts: 198
- Joined: Wed Oct 04, 2023 7:57 am
Re: Runtime error 70
where is it possible to download LpStudio?
is it freely available?
is it freely available?
Re: Runtime error 70
Thanks for answering!
It's a complicated question... LpStudio is pretty much abandonware now, since the publisher is no more, and it's more than 20 years old. I get it from my employer, and they still keep it quite close to their chest, so I think I could get into trouble if I shared it here (by potentially exposing my employer to some licensing issues).
It's a complicated question... LpStudio is pretty much abandonware now, since the publisher is no more, and it's more than 20 years old. I get it from my employer, and they still keep it quite close to their chest, so I think I could get into trouble if I shared it here (by potentially exposing my employer to some licensing issues).
Re: Runtime error 70
I've been tinkering with this problem on and off without finding a solution.
Could someone give me some guidance on what debug channels would be best to use when troubleshooting a copy/paste operation?
Could someone give me some guidance on what debug channels would be best to use when troubleshooting a copy/paste operation?
Re: Runtime error 70
I had a quick look at your debuglog which contains unfortunately a lot of lines that don't seem interesting. I would start by making a simpler debug log first like WINEDEBUG=+loaddll,+seh,+msgbox
Then look what dlls get loaded. I could see in your log some dll like msvbvm60 so maybe 'winetricks vb6run' might be interesting (you can see in winetricks source that it is in that verb:https://raw.githubusercontent.com/Winet ... winetricks).
Continue like so, trying some (ancient) winetricks verbs.
If that doesn't work out, you could try get WINEDEBUG=+relay,+seh,+msgbox log , and look before the 'msgbox' in the log, maybe that reveals something, or attach the log compressed here.
Then look what dlls get loaded. I could see in your log some dll like msvbvm60 so maybe 'winetricks vb6run' might be interesting (you can see in winetricks source that it is in that verb:https://raw.githubusercontent.com/Winet ... winetricks).
Continue like so, trying some (ancient) winetricks verbs.
If that doesn't work out, you could try get WINEDEBUG=+relay,+seh,+msgbox log , and look before the 'msgbox' in the log, maybe that reveals something, or attach the log compressed here.