New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOS4GW 2.01 #193

Open
javiergutierrezchamorro opened this Issue Aug 23, 2015 · 19 comments

Comments

Projects
None yet
4 participants
@javiergutierrezchamorro
Member

javiergutierrezchamorro commented Aug 23, 2015

I have achieved to get the permission from Terry Colligan at Tenberry, to redistribute latest dos4gw 2.01 into OpenWatcom, as an upgrade of current 1.97: http://www.tenberry.com/dos4g/watcom/rn4gw.html

It was a paid upgrade, that he is kindly providing to the project, on a royalte free basis.

Unfortunately his backup server got broken, and he will need about a month to recover it. In the meantime, we can upgrade dos4gw.exe in the repository, or either wait for the system restore when it happens, and then upgrade all the distribution files related to DOS4GW.

Is it interested for you? If so, I can handle it. Do you prefer to upgrade the exe now, and later related files, or do it at the same time?

Thanks.

@jmalak

This comment has been minimized.

Member

jmalak commented Aug 23, 2015

It is excellent, thanks for your effort.
We should do some testing with this new version of DOS4GW before we include it in OW 2.0 to be sure that no problem with compatibility. By example sampler, debugger, executable(stub) etc.

@jmalak

This comment has been minimized.

Member

jmalak commented Aug 23, 2015

Thanks for link.

@javiergutierrezchamorro

This comment has been minimized.

Member

javiergutierrezchamorro commented Aug 23, 2015

Tried creating a commit before, but could not with a pending pull request.

@jmalak

This comment has been minimized.

Member

jmalak commented Aug 23, 2015

You can, but you must create another branch.

@jmalak jmalak added the information label Oct 12, 2015

@Azarien

This comment has been minimized.

Contributor

Azarien commented Mar 6, 2016

DOS4GW 2.01a does not work with set DOS4G=QUIET

@jmalak

This comment has been minimized.

Member

jmalak commented Mar 6, 2016

What you mean by "does not work with set DOS4G=QUIET"?
Do you get banner, but application is running or not?

@javiergutierrezchamorro

This comment has been minimized.

Member

javiergutierrezchamorro commented Mar 7, 2016

Assuming DOS4G=QUIET works on 1.97, and not in 2.01a, and assuming the the documentation does not specify so, probably better thing would be report it to Tenberry.

At the moment DOW4GW 2.01a is only a binary distribution in OW. I am waiting for Terry for the full release yet.

@Azarien

This comment has been minimized.

Contributor

Azarien commented Mar 7, 2016

c:\>dos4gw
DOS/4GW Protected Mode Run-time  Version 2.01a
Copyright (c) Tenberry Software, Inc. 1996
DOS/4GW fatal error (1004): syntax is DOS4GW <executable.xxx>

c:\>set dos4g=quiet

c:\>dos4gw
DOS/4G error (5004): cfg syntax error - Invalid char after option string
DOS4G=quiet
           ^

This prevents an application from running.
I haven't tested other variables.
v 1.97 works fine.

@javiergutierrezchamorro

This comment has been minimized.

Member

javiergutierrezchamorro commented Mar 7, 2016

Agree Azarien.
Have been able to reproduce it both under DR-DOS 8 and under DOSBOX.
Hope Tenberry will answer your report.

@igorzhitko

This comment has been minimized.

igorzhitko commented Mar 7, 2016

Try set DOS4GW=STARTUPBANNER:OFF

@Azarien

This comment has been minimized.

Contributor

Azarien commented Mar 7, 2016

Doesn't seem to do anything (neither with DOS4G)

Maybe QUIET is simply not supported in 2.01. But the message is quite confusing.

@jmalak

This comment has been minimized.

Member

jmalak commented Mar 7, 2016

In release notes is following section

E ** Configuration has been enhanced for flexibility and consistency
across the DOS/4G Family of products. Most of the options have
remained the same. Please review chapter 4 of the the DOS/4G Family
Programmer's Guide for details.
Note: The new format for configuration options is not backwards
compatible with the 1.97 version configuration options. You must
convert your preexisting options to the new format or they will
not work.

It is problem with OW stub which use old parameter QUIET.
But OW 2.0 use stub without QUIET parameter that OW 2.0 compilers should work with DOS4GW 2.0x.

Please, could you check OW2.0 DOS compilers if they works with new DOS4GW.

@jmalak

This comment has been minimized.

Member

jmalak commented Mar 9, 2016

I added note to OW wiki about DOS4GW configuration to work properly with OW 2.0.
https://github.com/open-watcom/open-watcom-v2/wiki/Notes

@Azarien

This comment has been minimized.

Contributor

Azarien commented Mar 10, 2016

Is the documentation available online somewhere?

@javiergutierrezchamorro

This comment has been minimized.

Member

javiergutierrezchamorro commented Mar 10, 2016

We are waiting for Terry for the full release. At the moment, only EXE is legally entitled.

@javiergutierrezchamorro

This comment has been minimized.

Member

javiergutierrezchamorro commented Sep 13, 2017

Terry Colligan is facing some health issues, and have not been able to recover a full copy of DOS/4GW.
Anyway, he remember his authorization to include newer DOS/4GW.

Unfortunately have not been able to get full package from other sources yet. If any one has it, please attach it here so I can push to the repository.

In the meantime @jmalak can you please update bld/redist with this EXE only?
dos4gw 2.01a.zip

Thanks.

@javiergutierrezchamorro

This comment has been minimized.

Member

javiergutierrezchamorro commented Sep 17, 2018

Unfortunately Terry passed away a few months back:

Hope someone will have a full 2.01a copy to be integrated in Openwatcom. Will be a nice gift for remembering him.

@javiergutierrezchamorro

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment