New Build 1.0.614

  • Thread starter Thread starter Model-Behavior
  • Start date Start date
M

Model-Behavior

Hey, the new virgin of MASB installed automatically and
effortlessly!

But it's still "Beta 1" and I do not see one single
change or enhancement to the program whatsoever. :-(

Six months just to change the time bomb date?

No way, I must be missing something. Clue me in, where
are the changes and product enhancements?

Is there a strike going on at Microsoft? <just asking> :-
)

-MB
 
There is some significant "under the hood" work in this update--LSP stack
breakage is less likely, some scheduler details are fixed, but a new bug
seems to have been introduced there. Check the release notes in the product
help and at the download web site.
 
I still haven't had the time to test it. 12 hour time scheme users seem to
say it is better, 24 hour worse.

If you can switch to a 12 hour time scheme, that should fix it.

--
 
There is some significant "under the hood" work in this update--LSP
stack breakage is less likely, some scheduler details are fixed, but a
new bug seems to have been introduced there. Check the release notes
in the product help and at the download web site.
Click to expand...

They got the "flying windows" fixed. That's the one that annoyed me the
worst! Now I don't have to move my taskbar down to the bottom to trap them
anymore... :-)
 
Menno Hershberger said:
They got the "flying windows" fixed. That's the one that annoyed me the
worst! Now I don't have to move my taskbar down to the bottom to trap them
anymore... :-)
Click to expand...

One of the dialogs still flies, but it is one that fewer users will see- the
notification of updates available, as I understand it.
 
'cause all the complaints about PM times not working that I've seen are from
folks in locales where 24 hour settings are the default.

Looks like it is more subtle, perhaps, than simply 12 versus 24 hour
settings. There's a Dutch poster who has been suggesting resetting to US
timezones, and then making the settings and then resetting to the local
timezone, This seems rather strange to me--I need to get the time to test
it.

--
 
I've got this picture of one poor lone developer, originally from Giant,
forced to do maintenance programming on the old codebase. He deserves a
reward, and I'm glad I'm not on either end of the tug-of-war between the
Microsoft staff asking for fixes to the beta, and the managers resisting
spending the money.

--
 
Manual check for updates still keeps reinstalling 5729,
although about window shows 5729 installed. I diid the
upgrade thing in add/remove, but that did not fix it.
 
How do you change between 12 and 24 hr anyway?
-----Original Message-----
A bit slow here in the UK - sorry - I'm using 24 hr as
well.
-----Original Message-----
'cause all the complaints about PM times not working that I've seen are from
folks in locales where 24 hour settings are the default.

Looks like it is more subtle, perhaps, than simply 12 versus 24 hour
settings. There's a Dutch poster who has been suggesting resetting to US
timezones, and then making the settings and then resetting to the local
timezone, This seems rather strange to me--I need to get the time to test
it.
Click to expand...
..
... news:[email protected]
Click to expand...
..
Click to expand...
 
I don't know--I tend to largely ignore details of the windows shell and UI
operation--I'm a networking type, myself. I'm about 400 miles away from
home at a conference for a week, but I hope to get some time to investigate
this.

I'd be interested in knowing whether Tom Emmelot's suggestion of resetting
to a US timezone, setting the scan time, and then resetting to the UK
timezone works. This sounds like voodoo to me, but perhaps it is also a
language issue--perhaps locale is the right word rather than timezone.

--

RickyDick said:
How do you change between 12 and 24 hr anyway?
.
. in

.
Click to expand...
[/QUOTE]
 
I think I misstated Tom Emmelot's advice.

What are your language settings?

If they are other than US English, can you try:

reset language to US english
set scan time
reset language to whatever it was before

see whether scan time appears correct.

--

RickyDick said:
How do you change between 12 and 24 hr anyway?
.
. in

.
Click to expand...
[/QUOTE]
 
Back
Top