Program No Longer Can Save

David Baron · Post by **David Baron** » Tue Aug 30, 2011 5:27 am

Last week, Jammer Pro6 (a midi music program) could save its files just fine.
Today, I get that "program closing" wine errorbox and that's that.

What might be causing this? Running Debian Sid.

Post by **dimesio** » Tue Aug 30, 2011 5:39 am

David Baron wrote:Last week, Jammer Pro6 (a midi music program) could save its files just fine.
Today, I get that "program closing" wine errorbox and that's that.

What might be causing this? Running Debian Sid.

Did you upgrade Wine last week?

David Baron · Post by **David Baron** » Tue Aug 30, 2011 9:20 am

On Tuesday 30 Av 5771 17:02:02 [email protected] wrote:

David Baron wrote:
Last week, Jammer Pro6 (a midi music program) could save its files just
fine. Today, I get that "program closing" wine errorbox and that's
that.

What might be causing this? Running Debian Sid.
Did you upgrade Wine last week?

I believe there was an upgrade. But it had been working after the upgrade.
I have those libwine-***-unstable 1.1.35-1 packages

Another question is why there are two versions aound now? The ones not called
unstable which are 1.0.1-3.3 on SId and 1.1.24-2 on experimental and there are
these "-ustable" packages that are up to 1.1.35 on Sid.

David Baron · Post by **David Baron** » Tue Aug 30, 2011 1:52 pm

On Tuesday 30 Av 5771 17:19:13 David Baron wrote:

On Tuesday 30 Av 5771 17:02:02 [email protected] wrote:
David Baron wrote:
Last week, Jammer Pro6 (a midi music program) could save its files just
fine. Today, I get that "program closing" wine errorbox and that's
that.

What might be causing this? Running Debian Sid.
Did you upgrade Wine last week?
I believe there was an upgrade. But it had been working after the upgrade.
I have those libwine-***-unstable 1.1.35-1 packages

Another question is why there are two versions aound now? The ones not
called unstable which are 1.0.1-3.3 on SId and 1.1.24-2 on experimental
and there are these "-ustable" packages that are up to 1.1.35 on Sid.

So I compiled and installed the latest and greatest from winehq and got rid of
all of Debian's packages, just to see what happens.

Same thing. Possible that it is not a wine problem at all?

jjmckenzie · Post by **jjmckenzie** » Tue Aug 30, 2011 4:08 pm

On 8/30/11 7:19 AM, David Baron wrote:

On Tuesday 30 Av 5771 17:02:02 [email protected] wrote:
David Baron wrote:
Last week, Jammer Pro6 (a midi music program) could save its files just
fine. Today, I get that "program closing" wine errorbox and that's
that.

What might be causing this? Running Debian Sid.
Did you upgrade Wine last week?
I believe there was an upgrade. But it had been working after the upgrade.
I have those libwine-***-unstable 1.1.35-1 packages

Another question is why there are two versions aound now? The ones not called
unstable which are 1.0.1-3.3 on SId and 1.1.24-2 on experimental and there are
these "-ustable" packages that are up to 1.1.35 on Sid.

If you are looking at anything 1.0 or 1.1 they are very, very old. The
current stable version is 1.2.3 and the current 'development' version is
1.3.27.

You may need to build Wine from Source for Debian Sid.

James

David Baron · Post by **David Baron** » Wed Aug 31, 2011 6:43 am

On Tuesday 30 Av 5771 21:51:36 David Baron wrote:

On Tuesday 30 Av 5771 17:19:13 David Baron wrote:
On Tuesday 30 Av 5771 17:02:02 [email protected] wrote:
David Baron wrote: Did you upgrade Wine last week?
I believe there was an upgrade. But it had been working after the
upgrade. I have those libwine-***-unstable 1.1.35-1 packages

Another question is why there are two versions aound now? The ones not
called unstable which are 1.0.1-3.3 on SId and 1.1.24-2 on experimental
and there are these "-ustable" packages that are up to 1.1.35 on Sid.
So I compiled and installed the latest and greatest from winehq and got rid
of all of Debian's packages, just to see what happens.

Same thing. Possible that it is not a wine problem at all?

Whatever, the workaround I was able to do was copy comdlg32.dll from my old
windows 98 disk and set the application for windows 98. Have not checked for
any ill-effects from this yet ... The page fault in the debugger sited this
dll, the first recognizable object on its output. See if the thing still works
properly now that I can save files.

Hey, I have not run apps with native dlls for years. Originally, I always used
native windows totally, for better or worse, until upgrades of wine choked on
that. It was nice to have the old registry entries, i.e. for program
registrations, active. In the old days, this all worked flawlessly.

David Baron · Post by **David Baron** » Wed Aug 31, 2011 7:49 am

So I compiled and installed the latest and greatest from winehq and got
rid of all of Debian's packages, just to see what happens.

Same thing. Possible that it is not a wine problem at all?
Whatever, the workaround I was able to do was copy comdlg32.dll from my
old windows 98 disk and set the application for windows 98. Have not
checked for any ill-effects from this yet ... The page fault in the
debugger sited this dll, the first recognizable object on its output. See
if the thing still works properly now that I can save files.

Hey, I have not run apps with native dlls for years. Originally, I always
used native windows totally, for better or worse, until upgrades of wine
choked on that. It was nice to have the old registry entries, i.e. for
program registrations, active. In the old days, this all worked
flawlessly.

So, backtracking on some old problems:

WIth win98 dll and other windows, works fine but filenames do not show in the
dialog. Setting win98 and the filenames show, but ...

The 16-bit MIDI functionality thunks and that NEVER worked. Need a 32-bit
windows model to use the program.

I do not have a 32-bit windows available (maybe someone can send me the one
dll from y2k, maybe XP but there were compatability issues when that came out.
The versions with wine itself are fake and crash as before.

Post by **dimesio** » Wed Aug 31, 2011 9:02 am

David Baron wrote: I do not have a 32-bit windows available (maybe someone can send me the one
dll from y2k,

That would be illegal. Winetricks obtains dlls from legitimate download sources; check to see if it can get the ones you need.

David Baron · Post by **David Baron** » Wed Aug 31, 2011 10:41 am

On Wednesday 01 Elul 5771 18:02:28 [email protected] wrote:

I do not have a 32-bit windows available (maybe someone can send me the
one dll from y2k,
That would be illegal. Winetricks obtains dlls from legitimate download
sources; check to see if it can get the ones you need.

Nifty stuff. Unfortunately, this one is not on their list.

vitamin · Post by **vitamin** » Fri Sep 02, 2011 8:44 am

dimesio wrote:That would be illegal. Winetricks obtains dlls from legitimate download sources; check to see if it can get the ones you need.

Except you still have to have a valid Windows license to install such things, even with winetricks.

David Baron · Post by **David Baron** » Tue Sep 13, 2011 12:49 pm

This is not the true description. Comdlg32 crashes out even if I cancel.

Could this be relevant?
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x5a00001
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x5e00001

I can run the program (Jammer Pro 6) as Win98 with the dll copied from there
but even simply reading files with MIDI information chokes. I haver never been
able to run MIDI programs in Win98 mode in wine.

Problem started with the version of "wine-unstable" on Debian Sid and persists
in 3.1.28. I do not believe wine upgrading caused it but that wine is running
afoul of some other Sid upgrade on or around August 30.

David Baron · Post by **David Baron** » Wed Sep 21, 2011 10:47 am

On Tuesday 14 Elul 5771 20:45:18 David Baron wrote:

This is not the true description. Comdlg32 crashes out even if I cancel.

Could this be relevant?
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x5a00001
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x5e00001

I can run the program (Jammer Pro 6) as Win98 with the dll copied from
there but even simply reading files with MIDI information chokes. I haver
never been able to run MIDI programs in Win98 mode in wine.

Problem started with the version of "wine-unstable" on Debian Sid and
persists in 3.1.28. I do not believe wine upgrading caused it but that
wine is running afoul of some other Sid upgrade on or around August 30.

Bunch of tests --> BIG regression problem.

From WineHQ:
1.2.3 stable. Has error
1.3.28 unstable. Has error

From Debian Sid repos:
1.1.03 wine. Works like a charm
1.35 wine-unstable. Has error, except that a couple of weeks ago, I was using
this version perfectly. As I said, I believe some other upgrade is what broke
any and all newer wine versions. The old one, however still works.

BTW, suspecting problems with nvidia due to some postings here, I tested with
nouveau. Still failed. The oldest and goodest ran on nvidia right now.

Dewdman42 · Post by **Dewdman42** » Sat Apr 21, 2012 2:20 pm

Did you ever get this working? I'm using crossover games 10.3 and trying to get it work also. I immediately run into problems opening any file due to comdlg32 problem, I tried a comdlg32 from my xp install, but that didn't work either.

Really want to get this working on my mac somehow.

jjmckenzie · Post by **jjmckenzie** » Sun Apr 22, 2012 12:31 pm

On Sat, Apr 21, 2012 at 12:20 PM, Dewdman42 <[email protected]> wrote:

Did you ever get this working? I'm using crossover games 10.3 and trying to get it work also. I immediately run into
problems opening any file due to comdlg32 problem, I tried a comdlg32 from my xp install, but that didn't work either.

Two things: One, we do not support Crossover, any version or type here.
Two, Crossover 10.3 is very old and probably not supported any longer
by CodeWeavers.

Suggest that you install the released versions of Wine and try
installing/running this program in them. If you continue to
experience problems, we will try to assist.

James