Help: Visual Basic Setup Problems

  • Thread starter Thread starter Searcher7
  • Start date Start date
S

Searcher7

I picked up a book to learn Visual basic but cannot install it on my
system after I download it from this site: http://www.microsoft.com/express/Windows/.

I'm assuming my pc is the problem, but have no idea where to start.

It seems to stat installing, but then I get a pop-up that says:
"Microsoft Visual Basic 2008 Express Edition with SP1 - ENU has
encountered a problem during setup. Setup did not complete correctly."

Any help would be appreciated.

Thanks.

Darren Harris
Staten Island, New York.
 
Searcher7 said:
I picked up a book to learn Visual basic but cannot install it on my
system after I download it from this site:
http://www.microsoft.com/express/Windows/.

I'm assuming my pc is the problem, but have no idea where to start.

It seems to stat installing, but then I get a pop-up that says:
"Microsoft Visual Basic 2008 Express Edition with SP1 - ENU has
encountered a problem during setup. Setup did not complete correctly."
Click to expand...

Re-post to
"microsoft.public.vsnet.setup"
 
Searcher7 said:
I picked up a book to learn Visual basic but cannot install it on my
system after I download it from this site:
http://www.microsoft.com/express/Windows/.

I'm assuming my pc is the problem, but have no idea where to start.

It seems to stat installing, but then I get a pop-up that says:
"Microsoft Visual Basic 2008 Express Edition with SP1 - ENU has
encountered a problem during setup. Setup did not complete correctly."

Any help would be appreciated.
Click to expand...


Ralph told you the proper newsgroup to post to, but gave no explanation as
to why...and people posting for the first time (making an assumption) should
know why.

This newsgroup is for VB6 and under. There are significant differences
between VB6 and all later versions of what MS calls VB. Thus, there are
different newsgroups for each. The newsgroups for all versions AFTER VB6
have either "dotnet" or "vsnet" in their name. To confuse matters, MS
dropped the ".NET" from the product name. But it's still .NET and therefore
questions regarding it should be posted to a dotnet newsgroup.
 
Hi Mike,

Your last paragraph should have been left off. My reading of the title
this NG is that it is a VB NET newsgroup.


Regards,


Laurie
 
Hi,

Hmmmm

This message is multi-posted. Makes everything even more confusing than
need be.


Regards,
 
Your [Mike D's] last paragraph should have been left off.
My reading of the title this NG is that it is a VB NET
newsgroup.
Click to expand...

The OP cross posted to two groups, one of which (the dotnet.languages.vb
one) is the correct group for the product he is using and the other of which
is not. The OP needs to know that he should not have posted to the Classic
VB group regardless of whether or not his post was also cross posted to the
correct group.

To the OP: The comp.lang.basic.visual.misc group is the real Visual Basic
newsgroup and the last and final version of Visual Basic is VB6. The product
you are using, which is misleadingly called Visual Basic 2008 Express, is
NOT real Visual Basic. It is a variant of what is commonly called VB.Net and
your questions regarding it should NOT be either posted or cross posted to
the real Visual Basic group.

Generally, apart from a few very simple exceptions, VB6 code does not work
in VB.Net and VB.Net code does not work in VB6, and neither of them will
compile or run in the IDE of the other. They are as different as chalk and
cheese.

Unfortunately, in order to deliberately confuse the punters and to
dishonestly maximize profits, Micro$oft sprinkled their new and otherwise
completely different product with some Basic sounding constructs and gave it
a Basic sounding name and they pretended that it is the next version of
Visual Basic when in fact it is not. The name they have given to their new
product, the one you are using, is a deliberate lie. Micro$oft are lying
about it in much the same way that a food manufacturer would be lying if he
stuck "Cup a Soup" labels on packets of long grain rice, nothwithstanding
the fact that he might be the registered owner of the name "Cup a Soup". A
food manufacturer of course would be prosecuted in the courts of law for
such a deliberately dishonest act, but consumer law in most countries is
still decades behind the times and has not yet got its act together in
respect of software, although the EU is rapidly working towards it (which is
why Micro$oft hates us over here).

Your erroneous posting is not your fault of course because you have been
misled by Micro$oft and in the circumstances it is not surprising that you
have been taken in by Micro$oft's subterfuge and have cross posted to the
wrong group. Micro$oft would never openly acknowledge their dishonesty of
course, but they have tacitly admitted to it by creating a new and
completely different newsgroup on their own public servers for their new and
completely different product. To summarise, one of the groups you have
posted to, as mentioned above, is for the real Visual Basic and you should
not post or cross post any of your VB.Net questions to that group. If you
have questions about the imposter then you should post them to the
imposter's own newsgroup at:

microsoft.public.dotnet.languages.vb

Mike
 
Hello Mike ,

Did you ever considered a career as standup commedian ?
As i had again a big laugh about your analogy , in my opinion you are in
your way a true genius ! ;-)


Michel Posseth [MCP]
That guy that can code and is certified in VB and the imposter as you call
it i believe :-)



Mike Williams said:
Your [Mike D's] last paragraph should have been left off.
My reading of the title this NG is that it is a VB NET
newsgroup.
Click to expand...

The OP cross posted to two groups, one of which (the dotnet.languages.vb
one) is the correct group for the product he is using and the other of
which is not. The OP needs to know that he should not have posted to the
Classic VB group regardless of whether or not his post was also cross
posted to the correct group.

To the OP: The comp.lang.basic.visual.misc group is the real Visual Basic
newsgroup and the last and final version of Visual Basic is VB6. The
product you are using, which is misleadingly called Visual Basic 2008
Express, is NOT real Visual Basic. It is a variant of what is commonly
called VB.Net and your questions regarding it should NOT be either posted
or cross posted to the real Visual Basic group.

Generally, apart from a few very simple exceptions, VB6 code does not work
in VB.Net and VB.Net code does not work in VB6, and neither of them will
compile or run in the IDE of the other. They are as different as chalk and
cheese.

Unfortunately, in order to deliberately confuse the punters and to
dishonestly maximize profits, Micro$oft sprinkled their new and otherwise
completely different product with some Basic sounding constructs and gave
it a Basic sounding name and they pretended that it is the next version of
Visual Basic when in fact it is not. The name they have given to their new
product, the one you are using, is a deliberate lie. Micro$oft are lying
about it in much the same way that a food manufacturer would be lying if
he stuck "Cup a Soup" labels on packets of long grain rice,
nothwithstanding the fact that he might be the registered owner of the
name "Cup a Soup". A food manufacturer of course would be prosecuted in
the courts of law for such a deliberately dishonest act, but consumer law
in most countries is still decades behind the times and has not yet got
its act together in respect of software, although the EU is rapidly
working towards it (which is why Micro$oft hates us over here).

Your erroneous posting is not your fault of course because you have been
misled by Micro$oft and in the circumstances it is not surprising that you
have been taken in by Micro$oft's subterfuge and have cross posted to the
wrong group. Micro$oft would never openly acknowledge their dishonesty of
course, but they have tacitly admitted to it by creating a new and
completely different newsgroup on their own public servers for their new
and completely different product. To summarise, one of the groups you have
posted to, as mentioned above, is for the real Visual Basic and you should
not post or cross post any of your VB.Net questions to that group. If you
have questions about the imposter then you should post them to the
imposter's own newsgroup at:

microsoft.public.dotnet.languages.vb

Mike
Click to expand...
 
Michel Posseth [MCP]
That guy that can code and is certified in VB
and the imposter as you call it i believe :-)
Click to expand...

That guy who can code? So you think you're the only one do you?

Mike
 
Let me complain about the 'NEW' Chevy Camaro..
Even though it handles better than the 'Classic' Camaros
of the '60s,'70s, '80s AND '90s [lots of advertising stuff
snipped].. IT SHOULDN'T BE CALLED A CAMARO
Click to expand...

That's not the same thing at all. It is still a car and it can still drive
on the same roads and carry the same passengers and it can carry out all the
tasks that the old model could carry out in pretty much the same way. You
can pick it up from the showroom and drive it immediately and the very first
journey you do in it, no matter how long or complex it is, will take the
same time as it did before, or even less. If you could drive the old one
then you can immediately drive the new one, and you can drive it straight
away at the same speed in terms of getting things done as you could
previously. The new Camaro is basically the same product as the previous
one, with some added bells and whistles, and you can immediately drive it
and do the same things in it as you did before without the need to throw
away your old driving licence and learn to drive all over again. Also, the
people who make the new Camaro are not busy ripping up the roads or
modifying them in such a way that the old Camaro will no longer work on
them. The new Camaro is not a lie, unlike the supposedly new version of
Visual Basic, which is.

Personally I've got nothing against VB.Net, apart from that fact that it is
based on a lie. It might be a good thing and it might be absolute rubbish
and if Micro$oft had done the decent thing and had not dishonestly named it
and marketed it in a deliberate attempt to pretend it was something it is
not then I might have even given it a try myself, but I will certainly not
do so after being lied to by Micro$oft. If I ever to decide to move from VB6
it will be to something other than VB.Net, and whatever it is it will
certainly not be another Micro$oft product.

Mike
 
Your [Mike D's] last paragraph should have been left off.
 My reading of the title this NG is that it is a VB NET
newsgroup.
Click to expand...

The OP cross posted to two groups, one of which (the dotnet.languages.vb
one) is the correct group for the product he is using and the other of which
is not. The OP needs to know that he should not have posted to the Classic
VB group regardless of whether or not his post was also cross posted to the
correct group.

To the OP: The comp.lang.basic.visual.misc group is the real Visual Basic
newsgroup and the last and final version of Visual Basic is VB6. The product
you are using, which is misleadingly called Visual Basic 2008 Express, is
NOT real Visual Basic. It is a variant of what is commonly called VB.Net and
your questions regarding it should NOT be either posted or cross posted to
the real Visual Basic group.

Generally, apart from a few very simple exceptions, VB6 code does not work
in VB.Net and VB.Net code does not work in VB6, and neither of them will
compile or run in the IDE of the other. They are as different as chalk and
cheese.

Unfortunately, in order to deliberately confuse the punters and to
dishonestly maximize profits, Micro$oft sprinkled their new and otherwise
completely different product with some Basic sounding constructs and gaveit
a Basic sounding name and they pretended that it is the next version of
Visual Basic when in fact it is not. The name they have given to their new
product, the one you are using, is a deliberate lie. Micro$oft are lying
about it in much the same way that a food manufacturer would be lying if he
stuck "Cup a Soup" labels on packets of long grain rice, nothwithstanding
the fact that he might be the registered owner of the name "Cup a Soup". A
food manufacturer of course would be prosecuted in the courts of law for
such a deliberately dishonest act, but consumer law in most countries is
still decades behind the times and has not yet got its act together in
respect of software, although the EU is rapidly working towards it (whichis
why Micro$oft hates us over here).

Your erroneous posting is not your fault of course because you have been
misled by Micro$oft and in the circumstances it is not surprising that you
have been taken in by Micro$oft's subterfuge and have cross posted to the
wrong group. Micro$oft would never openly acknowledge their dishonesty of
course, but they have tacitly admitted to it by creating a new and
completely different newsgroup on their own public servers for their new and
completely different product. To summarise, one of the groups you have
posted to, as mentioned above, is for the real Visual Basic and you should
not post or cross post any of your VB.Net questions to that group. If you
have questions about the imposter then you should post them to the
imposter's own newsgroup at:

    microsoft.public.dotnet.languages.vb

Mike
Click to expand...

Ok. I didn't know any of this.(Not that there was any way to know
going by just the newsgroup titles).

I had run into a roadblock while studying assembly.(It was the book's
fault, not mine). I decided to look for an easier language to learn,
and one of the books I picked up and started reading is "Absolute
Beginner's Guide to Programming" (Third edition). By QUE(Greg Perry).

It is not specific about the "Visual Basic it discusses, so I assume
it is for nothing later than VB6.

So I'm now back to trying to figure out what to study first. Are there
any good *free* VB languages(downloads) that I should start with?

Thanks.

Darren Harris
Staten Island, New York.
 
So you think you're the only one do you?

No , but i do believe i am one of the few VB6 coders who can code reall VB6
and reall VB.Net code
and knows what both can and can`t .


Mike Williams said:
Michel Posseth [MCP]
That guy that can code and is certified in VB
and the imposter as you call it i believe :-)
Click to expand...

That guy who can code? So you think you're the only one do you?

Mike
Click to expand...
 
No , but i do believe i am one of the few VB6 coders who
can code reall VB6 and reall VB.Net code and knows
what both can and can`t .
Click to expand...

So there are only a very small number of people in the world who can code in
VB.Net and who have also coded in VB6, and you're one of them? That's very
clever of you. All those other less able people, especially those less able
people on the VB.Net group, must be very gad you're there to lead them
otherwise they would be wandering around like headless chickens. They must
be so proud of you.

Mike
 
Searcher7 said:
So I'm now back to trying to figure out what to study first. Are there
any good *free* VB languages(downloads) that I should start with?
Click to expand...

If you are just now starting to learn a programming language, and are
serious about learning to program (for the next several years) then I
would advise you to start with C# and not VB.

I started programming back in 1982, but got into programming for
Windows about 1995 using VB3. I enjoyed VB very much and got
pretty good at it (MS MVP 2004 -2008) but I just don't see the fun
in VB.Nxt anymore. I tried it early on (2000-2002) and have a copy
of Visual Studio 2005 & 2008, but for me the excitement has gone
with the advent of the .Net platform. Its just more work than fun,
than it used to be....

None the less, you can get started for free using MS's Express versions
(limited versions of the full fledged languages) and using C# puts you
inline for transitioning to other languages (esp. Java, C types, et al.) when
the time comes.

The way I see it, unless you already know VB, there are very few good
reasons to start learning (dotnet) programming with that language. At the
end of the day, every (dotnet) language they have has to deal with the
Common Language Runtime (CLR) and its framework of classes. Its
the mastery of that framework that you'll find takes the most work, no
matter what language you opt to try....

Have a look for yourself...
http://msdn.microsoft.com/en-us/vcsharp/default.aspx

LFS
 
Mike said:
So there are only a very small number of people in the world who can
code in VB.Net and who have also coded in VB6, and you're one of
them? That's very clever of you. All those other less able people,
especially those less able people on the VB.Net group, must be very
gad you're there to lead them otherwise they would be wandering
around like headless chickens. They must be so proud of you.
Click to expand...

I was a tad offended at first, but then I noticed he qualified his statement
with "reall".

I'm not sure I have ever written any reall VB6 or reall VB.Net code. so by
my very uncertainity, he is probably correct.

-ralph
 
It is not specific about the "Visual Basic it discusses, so I assume
it is for nothing later than VB6.

So I'm now back to trying to figure out what to study first. Are there
any good *free* VB languages(downloads) that I should start with?
VB.Net is free in the Expess version. That's
probably the only good option unless you want to
look into all of the third-party Basics. (There are
lots of oprions there, but I can never keep track
of them myself. :) VB6 is currently supported on
more systems than pretty much anything, and it's
dependency-free, for all practical purposes. But MS
no longer supports the product, there are no updates
expected, and it's hard to even find the CD to buy.

Microsoft started out with VB.Net
while phasing out VB support. They then just dropped
the ".net" as a marketing ploy. By naming VB.Net to
VB Microsoft went a long way toward making VB disappear.
(I've noticed that even most of the in-the-know
Slashdotters don't seem to be aware of the distinction.)

There was a related article awhile back, explaining
how Microsoft is trying the same ploy with C++:

http://www.regdeveloper.co.uk/2006/05/05/cplusplus_cli/

Of course, with a name as clunky as C++/CLI, it begs
to be shortened to just "C++". ... And voila, C++
becomes a .Net langauge. :)


It's confusing because the whole issue is politically
charged. Microsoft has been pushing .Net hard -- for
various reasons including stability, their desire
to eventually make money by renting software (you
can't rent people sofware if they can install something
better for free), and competition with Java server-side.

You just need to be aware that .Net is basically a
Java clone, OO, with huge dependencies, JIT compilation,
etc. Assembly is at the other extreme.
 
So there are only a very small number of people in the
world who can code in
VB.Net and who have also coded in VB6, and you're one of them?
That's very clever of you.
Click to expand...

But he can do it officially. He's certified.
Reall-y. :)
 
Searcher7 said:
I had run into a roadblock while studying assembly.(It was the book's
fault, not mine). I decided to look for an easier language to learn,
and one of the books I picked up and started reading is "Absolute
Beginner's Guide to Programming" (Third edition). By QUE(Greg Perry).
Click to expand...

BASIC is definitely a good 'Beginner's' language - it's in its name. <g>

It has a simple syntax, is easy to learn, run, and debug. MS's version in
the VB product ("Visual Basic Windows Development") would have been my
recommendation. Unfortunately it has been discontinued by MS, copies are
hard to come by, and never free. In fact VS6/VB6 continue to retail for
prices near what they sold for intially. (A definite testimony to its
popularity.)

There are other 'free' BASICS out there.

Taking MS up on their 'free' Express versions for the new .Net Framework
development is also a good option. Though I would agree with Larry. If you
have to learn something new then I would skip VB.Net.

But then there is also my favorite, which is a lousy *First* language for
someone totally new, but may be an option for someone with the nerve to take
on Assembly. <g>

That is C/C++. (You can download the MS VC++ Express version - for a 'free'
compiler). You don't have to jump into the .Net Framework. You can use the
Windows SDK, or start out writing simple console applications. There are
tons of "C" books available.

-ralph
 
But then there is also my favorite, which is a lousy *First*
language for someone totally new, but may be an option
for someone with the nerve to take on Assembly. <g>
Click to expand...

Assembly was once my favourite as well. Times have changed now of course and
hardware and operating systems are much more complex than they were, but
when I first started programming I found that machine code, initially
without the help of an Assembler and later with one, was just about the
simplest thing to deal with. I liked it on the grounds that it was very fast
and that once you had learned the basic machine code instruction set you
needed knowledge only of the operating system I/O functions and of the
addresses and functions of the various video and audio and other hardware
registers (there were far fewer of them of course in those days!). As far as
the actual coding was concerned you lived mostly by your own rules, and were
not required to either remember or to follow somebody else's. I actually
started with BASIC simply because a copy of it was built into the operating
system and I soon realised that (at least in those days of extremely slow
interpreted BASIC) it simply was not fast enough to do very much in real
time and so I bought a book on Assembly and I loved it. In fact one of the
very first really useful things I wrote in BASIC was a simple 6502
Assembler, which worked very well and which made it very much easier for me
to write my code. I was actually an engineer by trade, not a programmer, and
electronics was my only real hobby at the time, so I never paid as much
attention to my programming side-hobby as I perhaps should have done, but if
I had been a programmer by trade at the time I'm sure I would have stuck
with Assembler. In the end I let it go and concentrated almost totally on my
main hobby in electronics. It was many years later that I went back to
programming as a hobby. Too late for me now of course to move into Assembler
again, operating systems and hardware are vastly more complex than they were
and I am far too long in the tooth to begin learning their intricacies, so
Assembler is out for me and I'll stick to my favourite VB6 until it finally
gets ground into the dusts of time, by which time I will almost certainly be
in there with it ;-)

Mike
 
Hmm

I never looked at it from that perspective but..... i guess you might be
right so you might also include the vb classic group then

;-)

Are you now done roisterer? , you know exactly what i mean
 
Hmm I never looked at it from that perspective but..... i guess you might
be right so you might also include
the vb classic group then
Click to expand...

Please elucidate.
Are you now done roisterer? , you know exactly
what i mean
Click to expand...

I'm afraid I don't know exactly what you mean, Michelle. I know what
roisterer means of course, and it applies most aptly to your own behaviour
when you swaggered about telling the people on the newgsroup the uproarious
lie that you are /one of the few people/ who can actually code in VB6 and in
VB.Net. However your qualifying phrase, "you know exactly what I mean",
would seem to indicate that you actually mean something other than the
standard dictionary definition. So, once again Michelle, please elucidate.

Mike
 
Back
Top