Page 1 of 1

Problem with Level Manager

Posted: Fri Nov 24, 2017 6:43 pm
by Sascha81
Why make Level Manager in ConfEdit this:

Run-time error `70`:

Permission denied

^ How can i solve this problem? Why Permission denies?

Re: Problem with Level Manager

Posted: Sat Nov 25, 2017 4:36 pm
by Holger
Unfortunately, ConfEdit is very old software (written for Windows XP) with its source code lost a long time ago (at least that's what I assume), so problems with current operating systems (which I assume to be the cause for the described problem here) cannot be debugged or fixed anymore. :-(

Does this problem happen _always_ and in _all_ situations when invoking the function "Level Manager" in ConfEdit, or does it happen only on certain file systems, under certain circumstances or for certain files or directories?

But as said, I'm afraid that this problem cannot be solved anymore, so the corresponding functionality is probably lost. :-(

Re: Problem with Level Manager

Posted: Sun Nov 26, 2017 7:38 am
by Sascha81
This problem happen always

Re: Problem with Level Manager

Posted: Sun Nov 26, 2017 6:14 pm
by Holger
Then I think it cannot be fixed, unfortunately. :-(

Re: Problem with Level Manager

Posted: Tue Nov 28, 2017 1:22 am
by filbo
Make a Windows XP VM (under any of the dozen or so virtualization environments available these days). The old binary should run on it.

Strongly recommend you pre-configure the virtual hardware to have NO sort of networking, before ever booting XP in a VM. Transfer data to/from the VM with some safer mode like virtual floppies or 'host guest filesystem' -- some mechanism which does not allow anything from the Internet to sniff at the VM, since it will be pwned in milliseconds...

(It might also work under WINE on Linux / Mac -- a rare case where WINE's trailing-edge situation could be a benefit...)

Re: Problem with Level Manager

Posted: Mon Dec 04, 2017 11:40 am
by Holger
Yes, that's right -- as it was created for Windows XP, it should still run fine in a Windows XP VM.

Thanks for mentioning this workaround, filbo! :-)