By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,333 Members | 1,070 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,333 IT Pros & Developers. It's quick & easy.

VB.NET program crashes in Windows 98

P: n/a
I am about to release the second version of a program that I started writing
12 months ago. The first version worked fine on 98 upwards. This version
seems to crash on Windows 98. I realise that this is a bit vague, but anyone
any broad guidance as to how I might go about sorting this one?? To make
matters worse, It seems to work fine on a Windows 98 machine home - loaded
onto 2 at this other site with dotnet framework and it crashes. The initial
version is working OK on these external machines. I do not fancy a rather
long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they
were.

Any clues anyone?? Any particular calls, namespaces etc that are not too
well tolerated on Windows 98?? About to go nd try it on another Windows 98
machine here - and I hope that it crashes so that I have something to work
with!!

Best wishes

Paul Bromley
Nov 20 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
Do these 98 mcahines not have MDAC? Does your program require it?

www.microsoft.com/data

HTH,
Greg
"Paul Bromley" <fl*******@dsl.pipex.com> wrote in message
news:eR**************@TK2MSFTNGP09.phx.gbl...
I am about to release the second version of a program that I started writing 12 months ago. The first version worked fine on 98 upwards. This version
seems to crash on Windows 98. I realise that this is a bit vague, but anyone any broad guidance as to how I might go about sorting this one?? To make
matters worse, It seems to work fine on a Windows 98 machine home - loaded
onto 2 at this other site with dotnet framework and it crashes. The initial version is working OK on these external machines. I do not fancy a rather
long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they
were.

Any clues anyone?? Any particular calls, namespaces etc that are not too
well tolerated on Windows 98?? About to go nd try it on another Windows 98
machine here - and I hope that it crashes so that I have something to work
with!!

Best wishes

Paul Bromley

Nov 20 '05 #2

P: n/a
* "Paul Bromley" <fl*******@dsl.pipex.com> scripsit:
I am about to release the second version of a program that I started writing
12 months ago. The first version worked fine on 98 upwards. This version
seems to crash on Windows 98. I realise that this is a bit vague, but anyone
any broad guidance as to how I might go about sorting this one?? To make
matters worse, It seems to work fine on a Windows 98 machine home - loaded
onto 2 at this other site with dotnet framework and it crashes. The initial
version is working OK on these external machines. I do not fancy a rather
long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they
were.


Can you post the error message?

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
<URL:http://dotnet.mvps.org/dotnet/faqs/>
Nov 20 '05 #3

P: n/a
Hi Greg,

It doesn't need MDAC. I have installed a couple of my VB6 Programs on the
machines that do need MDAC and these do run OK.

Thanks.
Paul

"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Do these 98 mcahines not have MDAC? Does your program require it?

www.microsoft.com/data

HTH,
Greg
"Paul Bromley" <fl*******@dsl.pipex.com> wrote in message
news:eR**************@TK2MSFTNGP09.phx.gbl...
I am about to release the second version of a program that I started

writing
12 months ago. The first version worked fine on 98 upwards. This version
seems to crash on Windows 98. I realise that this is a bit vague, but

anyone
any broad guidance as to how I might go about sorting this one?? To make
matters worse, It seems to work fine on a Windows 98 machine home - loaded onto 2 at this other site with dotnet framework and it crashes. The

initial
version is working OK on these external machines. I do not fancy a rather long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they were.

Any clues anyone?? Any particular calls, namespaces etc that are not too
well tolerated on Windows 98?? About to go nd try it on another Windows 98 machine here - and I hope that it crashes so that I have something to work with!!

Best wishes

Paul Bromley


Nov 20 '05 #4

P: n/a
Is the program running local or from network drive?

Does it crash immediately on startup, or when you do something in
particular? Or does it seems random?

Greg

"Paul Bromley" <fl*******@dsl.pipex.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi Greg,

It doesn't need MDAC. I have installed a couple of my VB6 Programs on the
machines that do need MDAC and these do run OK.

Thanks.
Paul

"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Do these 98 mcahines not have MDAC? Does your program require it?

www.microsoft.com/data

HTH,
Greg
"Paul Bromley" <fl*******@dsl.pipex.com> wrote in message
news:eR**************@TK2MSFTNGP09.phx.gbl...
I am about to release the second version of a program that I started writing
12 months ago. The first version worked fine on 98 upwards. This version seems to crash on Windows 98. I realise that this is a bit vague, but

anyone
any broad guidance as to how I might go about sorting this one?? To make matters worse, It seems to work fine on a Windows 98 machine home - loaded onto 2 at this other site with dotnet framework and it crashes. The

initial
version is working OK on these external machines. I do not fancy a rather long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they were.

Any clues anyone?? Any particular calls, namespaces etc that are not too well tolerated on Windows 98?? About to go nd try it on another
Windows 98 machine here - and I hope that it crashes so that I have something to work with!!

Best wishes

Paul Bromley



Nov 20 '05 #5

P: n/a
Hi Greg,

Just tried it here on another of my Windows 98 machines and again it s
running OK. It crashed on these other machines at startup before any forms
are visualised. I have just had a look at the spec that I have written down
on paper and they only have 56meg of RAM. I suspect that this is probably
the issue, and that my first version was lighter on memory requirements. I
supppose that we get used to machines that are adequately specced these
days.

Best wishes

Paul Bromley

"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:u%****************@tk2msftngp13.phx.gbl...
Is the program running local or from network drive?

Does it crash immediately on startup, or when you do something in
particular? Or does it seems random?

Greg

"Paul Bromley" <fl*******@dsl.pipex.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi Greg,

It doesn't need MDAC. I have installed a couple of my VB6 Programs on the
machines that do need MDAC and these do run OK.

Thanks.
Paul

"Greg Burns" <greg_burns@DONT_SPAM_ME_hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Do these 98 mcahines not have MDAC? Does your program require it?

www.microsoft.com/data

HTH,
Greg
"Paul Bromley" <fl*******@dsl.pipex.com> wrote in message
news:eR**************@TK2MSFTNGP09.phx.gbl...
> I am about to release the second version of a program that I started
writing
> 12 months ago. The first version worked fine on 98 upwards. This version > seems to crash on Windows 98. I realise that this is a bit vague, but anyone
> any broad guidance as to how I might go about sorting this one?? To make > matters worse, It seems to work fine on a Windows 98 machine home -

loaded
> onto 2 at this other site with dotnet framework and it crashes. The
initial
> version is working OK on these external machines. I do not fancy a

rather
> long-winded approach out finding out why. I suppose I should have
> double-checked whether these 2 machines were SE or not - I think
that they
> were.
>
> Any clues anyone?? Any particular calls, namespaces etc that are not too > well tolerated on Windows 98?? About to go nd try it on another

Windows
98
> machine here - and I hope that it crashes so that I have something

to work
> with!!
>
> Best wishes
>
> Paul Bromley
>
>



Nov 20 '05 #6

P: n/a

Our program (VB .Net, VS 2003) works fine on Win98 2nd edition, but
crashes on win98 1st edition.

Right-click "My Computer".
Select "Properties".
Select "General" tab.
Look in the "System" paragraph
Win98 1st edition: 4.10.1998
Win98 2nd edition: 4.10.2222 A
Atara.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 20 '05 #7

P: n/a
I was told by one of the newsgroup replys that you couldn't run programs written in VB.net on Windows 95 but guess they will run on at least some W98 machines. Assume you have to install the .net framework on the 98 machine first. Is that correct?
--
Dennis in Houston
"Paul Bromley" wrote:
I am about to release the second version of a program that I started writing
12 months ago. The first version worked fine on 98 upwards. This version
seems to crash on Windows 98. I realise that this is a bit vague, but anyone
any broad guidance as to how I might go about sorting this one?? To make
matters worse, It seems to work fine on a Windows 98 machine home - loaded
onto 2 at this other site with dotnet framework and it crashes. The initial
version is working OK on these external machines. I do not fancy a rather
long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they
were.

Any clues anyone?? Any particular calls, namespaces etc that are not too
well tolerated on Windows 98?? About to go nd try it on another Windows 98
machine here - and I hope that it crashes so that I have something to work
with!!

Best wishes

Paul Bromley

Nov 20 '05 #8

P: n/a
Definately will run on W98SE (done it). From this thread I am beginning to
wonder about pre SE.

You always have to install the .Net Framework first for a .net program.
Until the OS has it preinstalled, and by then their will be newer version
out of anyways. :^) WinXP SP2 will have NET 1.1, no?

Greg
"Dennis" <De****@discussions.microsoft.com> wrote in message
news:09**********************************@microsof t.com...
I was told by one of the newsgroup replys that you couldn't run programs written in VB.net on Windows 95 but guess they will run on at least some W98
machines. Assume you have to install the .net framework on the 98 machine
first. Is that correct? --
Dennis in Houston
"Paul Bromley" wrote:
I am about to release the second version of a program that I started writing 12 months ago. The first version worked fine on 98 upwards. This version
seems to crash on Windows 98. I realise that this is a bit vague, but anyone any broad guidance as to how I might go about sorting this one?? To make
matters worse, It seems to work fine on a Windows 98 machine home - loaded onto 2 at this other site with dotnet framework and it crashes. The initial version is working OK on these external machines. I do not fancy a rather long-winded approach out finding out why. I suppose I should have
double-checked whether these 2 machines were SE or not - I think that they were.

Any clues anyone?? Any particular calls, namespaces etc that are not too
well tolerated on Windows 98?? About to go nd try it on another Windows 98 machine here - and I hope that it crashes so that I have something to work with!!

Best wishes

Paul Bromley

Nov 20 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.