System.IO and Windows 98

[jcrouse]

From what I can tell on Microsoft's website the .Net framework's System.IO
will not work with Windows 98. Is this true? I designed my app for use with
Windows 2000 and Windows XP. However, a user is trying in on a Windows 98
box and having some issues. I have labels which are filled by reading files
in the file system and he is telling me that they are not being filled. Is
this what I should expect?

Thanks,
John

 

[Herfried K. Wagner [MVP]]

From what I can tell on Microsoft's website the .Net framework's System.IO
will not work with Windows 98. Is this true? I designed my app for use with
Windows 2000 and Windows XP. However, a user is trying in on a Windows 98
box and having some issues. I have labels which are filled by reading files
in the file system and he is telling me that they are not being filled. Is
this what I should expect?

Most/everything(?) in the 'System.IO' namespace will work on Windows
98. Nevertheless, you should check the MSDN documentation for every
method. Without knowing your code it's impossible to tell you if your
problem is caused by the .NET Framework or your implementation.

 

[Cor Ligthert]

John,

We know a lot about your code, and you told it is not complex

So I think this cannot be an issue.

Is it only the labels that are not filled or stops the program. I thought
you are making a lot dynamicly, so it can be a memory issue, because people
who have Windows 98 computers have often very few memory for todays
standards.

Cor

 

[Jay B. Harlow [MVP - Outlook]]

John,
Where did you get that impression?

As Herfried suggests most of System.IO is fully functional under Windows 98!

You are correct in that Windows 98 does not support all the features of
Windows NT, 2000, XP, 2003, specifically the FileSystemWatcher & associated
classes are not supported as they require a NTFS drive...

For details of what is supported on which platform see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/framewkwinsupp.asp

Hope this helps
Jay

 

[jcrouse]

Cor,
You probably know my code better than me. I did not implement the
dynamic labels yet. I'm still trying to understand your code completely,
although I'm getting there. I'm trying to post fewer times and figure out
more on my own. If I just use your code and don't understand it, it makes
debugging impossible. Bear with me, I'll get there.

Thanks,
John

 

[jcrouse]

Jay,
That's where I got it. The column for "98 Me" says no to a lot of the
System and System.IO functions. Am I reading something wrong here?

Thanks,
John

 

[jcrouse]

Cor,
In case your wondering what you have put all this effort into you can
maybe get an idea form the app's homepage. You can check it out at
http://home.comcast.net/~cpviewer. Let me know your thoughts or questions.
Oh yeah, that's my first crack at a web site also. I wrote the app and
didn't have a way to distribute it. Man, FrontPage isn't very intuitive. Ya
know, I seem to be saying that about a lot of stuff lately. Maybe I don't
pick things us as quickly as I think or as I used to.

Later,
John

 

[Cor Ligthert]

John,

You probably know my code better than me. I did not implement the
dynamic labels yet. I'm still trying to understand your code completely,
although I'm getting there. I'm trying to post fewer times and figure out
more on my own. If I just use your code and don't understand it, it makes
debugging impossible. Bear with me, I'll get there.

You are completly right about this one.

My message about your code was meant to say that it is probably a lot of
code and can be everything, I found the answer from Jay very good where he
suggested about the watch.

Probably we do not know parts in your code that can be the problem, however
I seldom see people here in this newsgroup who are checking out problems
with more than 50 lines of code.

That was why I sand my message in the way that we do know your code.

I think you can better look on the classes you are using and check if there
is a more not normally often used one in it and check that than or ask in
this newsgroup if somebody knows that it will give problems with W98.

The most know one is the smptp server part CDO, however that was one of the
reason that I told we know your code because that I never saw in your code.

To explain a little bit why I wrote (We know your code)

Cor

 

[Jay B. Harlow [MVP - Outlook]]

John,

Am I reading something wrong here?

Yes! ;-)

You did notice that the second column of the table is a type (class,
structure, delegate, enum) from the namespace listed in the first column?

There are only 13 types from the System.IO namespace listed. 12 of those
types are specifically FileSystemWatcher related (either the class
specifically or its events, parameters to events or related enums). The 13th
ChangedFilters I don't see listed in MSDN... (searching MSDN for
ChangedFilters only turns up that page).


There are at least 29 types from System.IO that are not listed, for example
Stream, FileStream, MemoryStream, all the readers & writers are NOT listed
in that column, which means that all of them ARE available to use on Windows
98!


Hope this helps
Jay

 

[jcrouse]

Makes sense. Thanks for taking the time to explain.

John

 

[Jay B. Harlow [MVP - Outlook]]

John,
Are you still having problems with your program on Windows 98?

Or does your function use FileSystemWatcher?

Jay

Makes sense. Thanks for taking the time to explain.

John

<<snip>>

 

[jcrouse]

I'm not sure. It was one of my users and I haven't heard back. I am putting
together a 98SE box now to give it a go myself.

Thanks for the follow-up,
John