8-bit compatibility <complex issue>

[Guest]

The problem is somewhat convoluted ... My company uses a piece of software
that was built in the mid 80's and runs on a 16-bit subsystem, distriubted to
our clients. We have had some minor compatibility issues with XP in the
past, but have been able to remedy it by copying the shell.dll file to the
system32 folder, or restoring the .NT files in system32 dir. However after
the October 11 security patch, we have been experianceing more brakage of our
program. After further investigation, I have realized that the program uses
8-bit file handlers internally from pre-compiled libraries.

My question is threefold :
1) Did the October 11 patch alter the 16-bit subsystem that emulates the
8bit assembly? Is that why I am having an increase in problems?
2) Are we going to see the deteriotization of 8-bit assembly utilization?
3) Is there any article that has been published about this so far?

 

[David H. Lipman]

From: "IMOFirey" <[email protected]>

| The problem is somewhat convoluted ... My company uses a piece of software
| that was built in the mid 80's and runs on a 16-bit subsystem, distriubted to
| our clients. We have had some minor compatibility issues with XP in the
| past, but have been able to remedy it by copying the shell.dll file to the
| system32 folder, or restoring the .NT files in system32 dir. However after
| the October 11 security patch, we have been experianceing more brakage of our
| program. After further investigation, I have realized that the program uses
| 8-bit file handlers internally from pre-compiled libraries.
|
| My question is threefold :
| 1) Did the October 11 patch alter the 16-bit subsystem that emulates the
| 8bit assembly? Is that why I am having an increase in problems?
| 2) Are we going to see the deteriotization of 8-bit assembly utilization?
| 3) Is there any article that has been published about this so far?

A piece of software that is 15 to 20 yrs. old should be re-written and recompiled for
Today's Operating Systems.

It ridiculous to think that there should be backward compatibility for sotware that old.

That is your answer !

 

[Guest]

Well Unfortunately I dont have any control over the program itself, just the
support.

And being a cog in the corporate machine the best I can do is gather support
from these forums and from the Microsoft site to show that it is NOT going to
be supported and why.

 

[David H. Lipman]

From: "IMOFirey" <[email protected]>

| Well Unfortunately I dont have any control over the program itself, just the
| support.
|
| And being a cog in the corporate machine the best I can do is gather support
| from these forums and from the Microsoft site to show that it is NOT going to
| be supported and why.

I understand that support concept. You have to educate management that this is akin to a
mechanical part that has much wear and tare. As a function of time the mechanical component
will break and necesitate a replacement. It would be incumbant upon them to replace the
part before it is completely broken. Otherwise it may cause more trouble than the short
disruption caused by the short time to implement the replacement part.

Think of it as an old bald tire. Replace it before you go out on the road and the
replacemnt will have little impact. Derive on that bald tire and if you get a flat the
consequences will be far greater depending upon if there is a spare tire or if you are side
lined onto to the road side awaiting a service vehicle.

I this this should have been looked at ten years ago in what is called "preventative
maintenance". Every so often one must look at the applications and procedures being used in
a business model and revive them based upon current technology and changes in the industtry.

 

[Jim]

Well Unfortunately I dont have any control over the program itself, just
the
support.

And being a cog in the corporate machine the best I can do is gather
support
from these forums and from the Microsoft site to show that it is NOT going
to
be supported and why.

Ask Microsoft about this issue. This is a newsgroup, and our opinions are
not important.
Jim

 

[Guest]

Ask Microsoft about this issue. This is a newsgroup, and our opinions are
not important.
Jim

Yeah thats a great idea... Any idea where on god's green earth I could do
that? I mean its not like they post those things up front and all "if you
have compatibility issues with your software, just call here" Maybe if they
charge by the minute or something like a bad porn 900 number ...

I was hoping someone had heard of an article or something along those lines
I could use, now granted I didnt think there was, but I am getting to a "shot
in the dark" stage ...

I am gonna bounce around Microsoft's phones tomorrow and see what comes of it.

Thanks!

 

[Guest]

From: "IMOFirey" <[email protected]>

| Well Unfortunately I dont have any control over the program itself, just the
| support.
|
| And being a cog in the corporate machine the best I can do is gather support
| from these forums and from the Microsoft site to show that it is NOT going to
| be supported and why.

I understand that support concept. You have to educate management that this is akin to a
mechanical part that has much wear and tare. As a function of time the mechanical component
will break and necesitate a replacement. It would be incumbant upon them to replace the
part before it is completely broken. Otherwise it may cause more trouble than the short
disruption caused by the short time to implement the replacement part.

Think of it as an old bald tire. Replace it before you go out on the road and the
replacemnt will have little impact. Derive on that bald tire and if you get a flat the
consequences will be far greater depending upon if there is a spare tire or if you are side
lined onto to the road side awaiting a service vehicle.

I this this should have been looked at ten years ago in what is called "preventative
maintenance". Every so often one must look at the applications and procedures being used in
a business model and revive them based upon current technology and changes in the industtry.

That is a great metaphore, and if you dont mind I am going to use the
ideaolgy behind it. Unfortunately it doesnt hold completely with the
setting, because we would then be saying that the road is wearing out... but
I the code for this program is definately balding ...

 

[David H. Lipman]

From: "IMOFirey" <[email protected]>


| That is a great metaphore, and if you dont mind I am going to use the
| ideaolgy behind it. Unfortunately it doesnt hold completely with the
| setting, because we would then be saying that the road is wearing out... but
| I the code for this program is definately balding ...

It just so happens roads do wear out. As trucks and cars pass over them as a function of
time, you will see the following...
cracks in pavement/cement
holes
tire goove patterns
ground slump where what was a flat road now exibits areas where the ground now has small
valleys

In this case, the roadbed needs to be resurfaced and replaced. ;-)

 

[David H. Lipman]

From: "IMOFirey" <[email protected]>


| Yeah thats a great idea... Any idea where on god's green earth I could do
| that? I mean its not like they post those things up front and all "if you
| have compatibility issues with your software, just call here" Maybe if they
| charge by the minute or something like a bad porn 900 number ...
|
| I was hoping someone had heard of an article or something along those lines
| I could use, now granted I didnt think there was, but I am getting to a "shot
| in the dark" stage ...
|
| I am gonna bounce around Microsoft's phones tomorrow and see what comes of it.
|
| Thanks!

The only way to get specific information would be supply the compiler and code base that the
software was created in and the requirements that is needed to execute the software in a MS
Windows environment.