military time

  • Thread starter Thread starter Fred K.
  • Start date Start date
F

Fred K.

I have installed the latest beta on the antispyware.
When I tell it to do my scanning at 22:00:00 hours, it
refuses to understand that it is 10 pm and it tries to do
my scanning at 10 am instead.
Any help available here?
 
Fred K. said:
I have installed the latest beta on the antispyware.
When I tell it to do my scanning at 22:00:00 hours, it
refuses to understand that it is 10 pm and it tries to do
my scanning at 10 am instead.

1. Configure Windows to use a 12-hour AM/PM time format.
2. Configure your MSAS schedules in 12-hour AM/PM format.
3. Configure Windows back into your preferred 24-hour format.
 
Fred said:
I have installed the latest beta on the antispyware.
When I tell it to do my scanning at 22:00:00 hours, it
refuses to understand that it is 10 pm and it tries to do
my scanning at 10 am instead.
Any help available here?

No help, Fred. But I can confirm that it is a definite bug.

BTW, using the workaround that Robin posted doesn't work. I changed my
system to use the 12 hour clock (AM/PM) and set AntiSpyware to 8:30 PM.
When I reset my system to use a 24 hour clock and then re-checked
AntiSpyware it had reset to 8:30 in the morning.

IOW, there does not seem to be any way to schedule a scan in the PM if
your system uses military (24 hour) time as default. Note that I have
not tested this to see what happens, but since AntiSpyware always shows
morning hours after an update, I would not expect an afternoon scan to
happen.
 
Hello Sky,

try this:

Go to start/Control Panel/Country settings
Change Language to US Inglisch.
Close with OK or Apply
Open MSA change all your time settings the way you wont.
Then go back to set your default Language.
MSA will scan and update on the right time!


With Regards >*< TOM >*<

Sky King schreef:
 
Hi Sky King.
I totally concur about what you said and in addition,
there are two different clocks in AntiSpyware.
For scanning you have a choice on am/pm or 24 hour clock
system depending on what is the computer setting is. On
the update clock you have a choice only for am/pm.
I hope the people at Microsoft are reading this.

-----------------------------------
 
Fred K. said:
there are two different clocks in AntiSpyware.
For scanning you have a choice on am/pm or 24 hour clock
system depending on what is the computer setting is. On
the update clock you have a choice only for am/pm.

What really matters is when AntiSpyware does the scheduled thing. You
should disregard the displayed time (which is subject to time-format
errors), and determine when the action really occurs.
 
Hi, Tom;

My system is already set to use US English. Changing it to something
else (UK English, for example) does not fix the problem in MSAS.
 
Hi, Robin;

I set MSAS to scan at 2200 yesterday (8 PM). When I applied the setting
it changed the MSAS display to 08:00 as expected. I left it alone, and
the scan took place at 08:00 AM today.

So with my system set to military time I am not able to schedule a scan
in the PM.
 
Hi, Fred;
Hi Sky King.
I totally concur about what you said and in addition,
there are two different clocks in AntiSpyware.
For scanning you have a choice on am/pm or 24 hour clock
system depending on what is the computer setting is. On
the update clock you have a choice only for am/pm.

Yeah, I saw that. And it brings up another bug:::: When does auto
update take place if one sets that option to "Every Week" and "2 AM" ???
<g>

Does anyone know if these time oddities were in the original Giant
package or were they introduced after MS modifications to the code?

--

....Sky

Build .615
=======
 
Hello Sky,

try this:

Goto: Start/Control Panel/Add-Remove programs/MSAS
then click on suport info!!!
Then click on repair!

With Regards >*< TOM >*<

Sky King schreef:
 
Sky King said:
My system is already set to use US English. Changing it to something
else (UK English, for example) does not fix the problem in MSAS.

Tom is not correct in just advising US English. The real point is that you
need to configure Windows into a 12-hour AM/PM time format before setting
any MSAS schedule time. After setting the schedule, you can revert to
24-hour time format. Tom's adice would only work if the US locale were
configured to 12-hour AM/PM, which it is by default, but not if customised
to 24-hour format by the user.
 
Sky King said:
I set MSAS to scan at 2200 yesterday (8 PM). When I applied the
setting it changed the MSAS display to 08:00 as expected. I left it
alone, and the scan took place at 08:00 AM today.

Did you configure the scheduled scan time in MSAS while Windows was
configured into a 12-hour AM/PM time format?
 
Robin said:
Did you configure the scheduled scan time in MSAS while Windows was
configured into a 12-hour AM/PM time format?

Yes, that seems to work as long as I don't go back into MSAS after
making the change back to 24-hour time.

Not an acceptable solution for release, but guess it will have to do
until we get the next build. :)
 
I'm hearing strongly from the groups that the solid 24 versus 12 hour time
format issue is new with build .613 and later.

There is at least one poster who really has an intriguing issue--he has
(apparently) a non-default format setting, and most, but not all of the
time, the program considers itself expired at startup. However, if he tries
multiple times, he can apparently get it to run eventually. This sound to
me as though there's an overflow involving the seconds digits or something
like this.

At any rate, unless folks really raise a fuss here, this probably won't
change before beta2.

--
 
Hello Bill,

I did all kind of install test with old versions of MSAS and Def files,
I clean out the whole Computer with the last install, so nothing old
left (maps/files, also those 3 in system32)also wipe out temp/temp
internet files, Regclean also done.
So if I (Dutch 24 hour default), do the Language trick to English(VS),
(default 12 hour) still here no problems after I go back to Dutch!!!!
So advice to those that have any problems it all kind:

uninstall, Delete MSAS folder and
delete in C:\windows\system32 the following files:
GCCollection.dll
hashlib.dll
gcUnCompress.dll

run a regceaner (Ccleaner)

http://www.ccleaner.com/ccdownload.asp

Also use the temp cleaner of Ccleaner.

Do a fresh install with version .615 (latest)
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

Working this way you know that you are really running .615 with all old
things not anymore on the system!!!

The old bugs are not away ;)

Regards >*< TOM >*<
 
This is an unusual beta in ways that won't be completely clear until we see
beta2, I believe. Indeed--old bugs will persist as long as we are using
beta1 code. Presumably there will be new bugs with beta2, but lets hope
they will be fewer and more subtle!

--
 
Bill,

Because this bug does not prevent a scan from running (it just runs at an
incorrect time). This is not something that will be fixed in a refresh
build. I do understand it is something which can be annoying to people who
run on 24 hour time and it is currently slated to be fixed in B2.

--
-steve

Steve Dodson
Microsoft Corporation
CISSP, MCSE
http://blogs.technet.com/stevedod
 
Missed this thread for awhile--sorry.

I hear you on the time issue being fixed in beta2--enough said!
 
Back
Top