W2K3 upgrade from W2K and DOS application

I just completed an in place upgrade from W2K to W2K3 and our company still
uses a DOS application that ran perfectly fine on the W2K3 server from a
mapped drive. Now after the upgrade the program starts, but when trying to
write to the program, which is simple dat files, we get an error indicating
end of file/disk and not able to read drive. I tried restoring the folder
and data, but that didn't help. For the time being I moved the folder/data
to a an XP workstation and am running it locally.

The article doesn't mention DOS, but it applies too.

811497 - Error Message When Windows 95 or Windows NT 4.0 Client
Logs On to Windows Server 2003 Domain
http://support.microsoft.com/default...b;en-us;811497


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------



"(E-Mail Removed)" <(E-Mail Removed)> wrote in
message news:7FE05556-6009-41D9-A8BF-(E-Mail Removed)...
> I just completed an in place upgrade from W2K to W2K3 and our company
still
> uses a DOS application that ran perfectly fine on the W2K3 server from a
> mapped drive. Now after the upgrade the program starts, but when trying
to
> write to the program, which is simple dat files, we get an error
indicating
> end of file/disk and not able to read drive. I tried restoring the folder
> and data, but that didn't help. For the time being I moved the
folder/data
> to a an XP workstation and am running it locally.

I wasn't clear. The client is not running DOS, the application is DOS, but
runs under Windows XP and used to be able to execute and write to the data
files from the W2K server.

"Phillip Windell" wrote:

> The article doesn't mention DOS, but it applies too.
>
> 811497 - Error Message When Windows 95 or Windows NT 4.0 Client
> Logs On to Windows Server 2003 Domain
> http://support.microsoft.com/default...b;en-us;811497
>
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
> -----------------------------------------------------
> Understanding the ISA 2004 Access Rule Processing
> http://www.isaserver.org/articles/IS...cessRules.html
>
> Microsoft Internet Security & Acceleration Server: Guidance
> http://www.microsoft.com/isaserver/t...dance/2004.asp
> http://www.microsoft.com/isaserver/t...dance/2000.asp
>
> Microsoft Internet Security & Acceleration Server: Partners
> http://www.microsoft.com/isaserver/partners/default.asp
> -----------------------------------------------------
>
>
>
> "(E-Mail Removed)" <(E-Mail Removed)> wrote in
> message news:7FE05556-6009-41D9-A8BF-(E-Mail Removed)...
> > I just completed an in place upgrade from W2K to W2K3 and our company
> still
> > uses a DOS application that ran perfectly fine on the W2K3 server from a
> > mapped drive. Now after the upgrade the program starts, but when trying
> to
> > write to the program, which is simple dat files, we get an error
> indicating
> > end of file/disk and not able to read drive. I tried restoring the folder
> > and data, but that didn't help. For the time being I moved the
> folder/data
> > to a an XP workstation and am running it locally.
>
>
>

did u check the share/ntfs permissions?

"(E-Mail Removed)" <(E-Mail Removed)> wrote in
message news:7FE05556-6009-41D9-A8BF-(E-Mail Removed)...
>I just completed an in place upgrade from W2K to W2K3 and our company still
> uses a DOS application that ran perfectly fine on the W2K3 server from a
> mapped drive. Now after the upgrade the program starts, but when trying
> to
> write to the program, which is simple dat files, we get an error
> indicating
> end of file/disk and not able to read drive. I tried restoring the folder
> and data, but that didn't help. For the time being I moved the
> folder/data
> to a an XP workstation and am running it locally.

I did and they were wide open just like before the upgrade. Once again this
was an in place upgrade of a production W2K server that was completed over
the weekend and upgraded to W2K3, so in theory the rights shouldn't have
changed.

"seth" wrote:

> did u check the share/ntfs permissions?
>
> "(E-Mail Removed)" <(E-Mail Removed)> wrote in
> message news:7FE05556-6009-41D9-A8BF-(E-Mail Removed)...
> >I just completed an in place upgrade from W2K to W2K3 and our company still
> > uses a DOS application that ran perfectly fine on the W2K3 server from a
> > mapped drive. Now after the upgrade the program starts, but when trying
> > to
> > write to the program, which is simple dat files, we get an error
> > indicating
> > end of file/disk and not able to read drive. I tried restoring the folder
> > and data, but that didn't help. For the time being I moved the
> > folder/data
> > to a an XP workstation and am running it locally.
>
>
>

In news:F2564011-62CA-4F92-9257-(E-Mail Removed),
(E-Mail Removed) <(E-Mail Removed)> typed:
> I did and they were wide open just like before the upgrade. Once again
> this was an in place upgrade of a production W2K server that was
> completed over the weekend and upgraded to W2K3, so in theory the rights
> shouldn't have changed.

Look up "Application Compatibility Mode" under the Help & Support. That
covers this situation. You need to make the DOS app think it is running on
Win2K still.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

if the dos app is running from the network drive then compatibility cannot
be set

"Todd J Heron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In news:F2564011-62CA-4F92-9257-(E-Mail Removed),
> (E-Mail Removed) <(E-Mail Removed)> typed:
>> I did and they were wide open just like before the upgrade. Once again
>> this was an in place upgrade of a production W2K server that was
>> completed over the weekend and upgraded to W2K3, so in theory the rights
>> shouldn't have changed.
>
> Look up "Application Compatibility Mode" under the Help & Support. That
> covers this situation. You need to make the DOS app think it is running
> on
> Win2K still.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>

Seth;

You are correct the application and data all run from the W2K3 server. It
used to all run under W2K, but after the in place upgrade that is when the
problems started. I am going to restore the data and reset the rights once
again, just in case something goofy affected it that I am not seeing.

"seth" wrote:

> if the dos app is running from the network drive then compatibility cannot
> be set
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > In news:F2564011-62CA-4F92-9257-(E-Mail Removed),
> > (E-Mail Removed) <(E-Mail Removed)> typed:
> >> I did and they were wide open just like before the upgrade. Once again
> >> this was an in place upgrade of a production W2K server that was
> >> completed over the weekend and upgraded to W2K3, so in theory the rights
> >> shouldn't have changed.
> >
> > Look up "Application Compatibility Mode" under the Help & Support. That
> > covers this situation. You need to make the DOS app think it is running
> > on
> > Win2K still.
> >
> > --
> > Todd J Heron, MCSE
> > Windows Server 2003/2000/NT; CCA
> > ----------------------------------------------------------------------------
> > This posting is provided "as is" with no warranties and confers no rights
> >
>
>
>

did u see my previous question asking if u checked the obvious like
share/ntfs permissions?
the folder might be shared with full control, but the ntfs permissions could
have something like "administrators/full control; domain
users/read,read&execute,list folder contents" which would cause the app to
not be able to write and cause the problem u experience

"(E-Mail Removed)" <(E-Mail Removed)> wrote in
message news:441F02DE-B7C0-4639-9777-(E-Mail Removed)...
> Seth;
>
> You are correct the application and data all run from the W2K3 server. It
> used to all run under W2K, but after the in place upgrade that is when the
> problems started. I am going to restore the data and reset the rights
> once
> again, just in case something goofy affected it that I am not seeing.
>
> "seth" wrote:
>
>> if the dos app is running from the network drive then compatibility
>> cannot
>> be set
>>
>> "Todd J Heron" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > In news:F2564011-62CA-4F92-9257-(E-Mail Removed),
>> > (E-Mail Removed) <(E-Mail Removed)> typed:
>> >> I did and they were wide open just like before the upgrade. Once
>> >> again
>> >> this was an in place upgrade of a production W2K server that was
>> >> completed over the weekend and upgraded to W2K3, so in theory the
>> >> rights
>> >> shouldn't have changed.
>> >
>> > Look up "Application Compatibility Mode" under the Help & Support.
>> > That
>> > covers this situation. You need to make the DOS app think it is
>> > running
>> > on
>> > Win2K still.
>> >
>> > --
>> > Todd J Heron, MCSE
>> > Windows Server 2003/2000/NT; CCA
>> > ----------------------------------------------------------------------------
>> > This posting is provided "as is" with no warranties and confers no
>> > rights
>> >
>>
>>
>>

The NTFS rights were correct, at least as viewed from the parent down, and
into several file folders and files, but after resetting the rights
everything started working. Thanks for your time.

"seth" wrote:

> did u see my previous question asking if u checked the obvious like
> share/ntfs permissions?
> the folder might be shared with full control, but the ntfs permissions could
> have something like "administrators/full control; domain
> users/read,read&execute,list folder contents" which would cause the app to
> not be able to write and cause the problem u experience
>
> "(E-Mail Removed)" <(E-Mail Removed)> wrote in
> message news:441F02DE-B7C0-4639-9777-(E-Mail Removed)...
> > Seth;
> >
> > You are correct the application and data all run from the W2K3 server. It
> > used to all run under W2K, but after the in place upgrade that is when the
> > problems started. I am going to restore the data and reset the rights
> > once
> > again, just in case something goofy affected it that I am not seeing.
> >
> > "seth" wrote:
> >
> >> if the dos app is running from the network drive then compatibility
> >> cannot
> >> be set
> >>
> >> "Todd J Heron" <(E-Mail Removed)> wrote in message
> >> news:(E-Mail Removed)...
> >> > In news:F2564011-62CA-4F92-9257-(E-Mail Removed),
> >> > (E-Mail Removed) <(E-Mail Removed)> typed:
> >> >> I did and they were wide open just like before the upgrade. Once
> >> >> again
> >> >> this was an in place upgrade of a production W2K server that was
> >> >> completed over the weekend and upgraded to W2K3, so in theory the
> >> >> rights
> >> >> shouldn't have changed.
> >> >
> >> > Look up "Application Compatibility Mode" under the Help & Support.
> >> > That
> >> > covers this situation. You need to make the DOS app think it is
> >> > running
> >> > on
> >> > Win2K still.
> >> >
> >> > --
> >> > Todd J Heron, MCSE
> >> > Windows Server 2003/2000/NT; CCA
> >> > ----------------------------------------------------------------------------
> >> > This posting is provided "as is" with no warranties and confers no
> >> > rights
> >> >
> >>
> >>
> >>
>
>
>