OK, what now concerning 5728?

[Clark]

It seems to me that 5728 was a special edition put out for some purpose, and
in my case was unable to handle some things 5600 could (I did report them).
Since MS has stopped downloads of 5728, have they also stopped taking
information about it from the Beta Testers? If that is the case, or simply
the fact that 5600 is still downloadable, would it be advisable for everyone
running 5728 to go back to 5600? I might suggest this because it appears
5600 is the REAL predecessor to the next release (final or otherwise) and
not 5728.

Clark

 

[Dan W.]

It seems to me that 5728 was a special edition put out for some purpose,
and in my case was unable to handle some things 5600 could (I did report
them). Since MS has stopped downloads of 5728, have they also stopped
taking information about it from the Beta Testers? If that is the case,
or simply the fact that 5600 is still downloadable, would it be
advisable for everyone running 5728 to go back to 5600? I might suggest
this because it appears 5600 is the REAL predecessor to the next release
(final or otherwise) and not 5728.

Clark

I am still using and testing 5728 which indeed does seem to be more bug
prone than build 5600. I have no intention of downgrading to build 5600
especially since another and possibly the final build is set to release
sometime this month. I will just download and install that build when
it is available to me or hopefully Microsoft may send me a DVD of it
which would be really sweet.

 

[BChat]

It seems to me that 5728 was a special edition put out for some purpose,
and in my case was unable to handle some things 5600 could (I did report
them). Since MS has stopped downloads of 5728, have they also stopped
taking information about it from the Beta Testers? If that is the case,
or simply the fact that 5600 is still downloadable, would it be
advisable for everyone running 5728 to go back to 5600? I might suggest
this because it appears 5600 is the REAL predecessor to the next release
(final or otherwise) and not 5728.

Clark

I am still using and testing 5728 which indeed does seem to be more bug
prone than build 5600. I have no intention of downgrading to build 5600
especially since another and possibly the final build is set to release
sometime this month. I will just download and install that build when
it is available to me or hopefully Microsoft may send me a DVD of it
which would be really sweet.

--
Dan W.
Computer User

I found 5600 to be a better build than 5728 too - more of my hardware
worked. I thought of going
back to it, but I didn't. IF I get the chance to get another build, I will,
and see how that goes.
This is my 1st OS beta testing experience, learned a lot, laughed a lot, and
swore some too ;-)

 

[Dan W.]

I am still using and testing 5728 which indeed does seem to be more bug
prone than build 5600. I have no intention of downgrading to build 5600
especially since another and possibly the final build is set to release
sometime this month. I will just download and install that build when
it is available to me or hopefully Microsoft may send me a DVD of it
which would be really sweet.

Actually, it is the first beta operating system that I have done as
well. I have tested other programs in beta status but not an operating
system. BTW, one development that I have found is with Vista that it is
always a good idea to try and see if the XP driver works first before
trying a beta driver that may not work.
When I upgrade to the next build, I plan on doing a clean install
and then seeing if I can get the Sound Blaster Audigy to work
effectively using the latest XP driver since the Vista driver(s) is in
beta status and does not work for me. I managed to get a little sound
out of one speaker but that was about it. Fortunately, my printer works
with the latest XP driver and it is an Epson Stylus C64.
BTW, does anyone know how to disable the print monitoring so I can
print until I can see that the cartridge is empty rather than being told
I have an empty cartridge when I know it can print a few more pages okay
and so I want the printer to try and print the papers. I do not want to
be ruled anymore by a printer that tells me that I don't have any ink in
the cartridge when I know I have ink left. If I need to use a hack for
this then I am willing to do that because it is annoying and I think the
printer manufacturers should get in trouble for this because they are
taking advantage of all of us.

 

[BChat]

Actually, it is the first beta operating system that I have done as
well. I have tested other programs in beta status but not an operating
system. BTW, one development that I have found is with Vista that it is
always a good idea to try and see if the XP driver works first before
trying a beta driver that may not work.
When I upgrade to the next build, I plan on doing a clean install
and then seeing if I can get the Sound Blaster Audigy to work
effectively using the latest XP driver since the Vista driver(s) is in
beta status and does not work for me. I managed to get a little sound
out of one speaker but that was about it. Fortunately, my printer works
with the latest XP driver and it is an Epson Stylus C64.
BTW, does anyone know how to disable the print monitoring so I can
print until I can see that the cartridge is empty rather than being told
I have an empty cartridge when I know it can print a few more pages okay
and so I want the printer to try and print the papers. I do not want to
be ruled anymore by a printer that tells me that I don't have any ink in
the cartridge when I know I have ink left. If I need to use a hack for
this then I am willing to do that because it is annoying and I think the
printer manufacturers should get in trouble for this because they are
taking advantage of all of us.
Dan W.
Computer User
----------------------------
I have trouble with SoundBlaster Audigy - sound OK, but it does funny things
to the record
tab in the control panel/sound area. My HP 7760 had to be installed as a
7780
no big deal, and my Epson scanner won't work at all - yet it did in 5600.

I am surprised at all the problems with AV programs - I'd have thought that
would be area
they'd all be on top of. I am also surprised MS doesn't include an AV
feature right in the OS,
it would compliment the firewall. It is too bad for if Symantec doesn't like
the idea - I don't like them ;-)

 

[Jupiter Jones [MVP]]

Microsoft accepts and looks a bugs for all builds AFAIK.
For obvious reasons, the newer builds will be more valid since fewer of the
bugs have been reported/resolved.

5728 is a better version if you are interested in giving more current
information to Microsoft.
The older builds are more likely to have the bug resolved or not even
relevant in a newer build.
Since 5728 is not a RC or even milestone build, there was not as much a
requirement for stability and performance as an RC so it is reasonable for
it to seem a little rougher.
Do not make the mistake in thinking a later build is automatically better in
all respects.
If you just want to run it for yourself, stick with what seems to run the
best, regardless the build.

Also, if you are asking here, you are probably not a Technical Beta Tester
but are probably a member of the Customer Preview Program.
Two different program with different purposes.

 

[Kirk]

Actually, I've had less problems with 5728 then I did with 5600. I'm able
to install more of my s/w and at least get my HP7200 to be recognized using
the MS driver and it seems to be a whole lot more stable (and 5600 was/is
pretty stable).

Kirk

 

[Rock]

It seems to me that 5728 was a special edition put out for some purpose,
and in my case was unable to handle some things 5600 could (I did report
them). Since MS has stopped downloads of 5728, have they also stopped
taking information about it from the Beta Testers?

<snip>

No bug information is important in all builds. I don't see any reason to go
back to 5600 unless you some some specific testing need. Remember running
any of these builds is for testing purposes.