We have a customer who is loading one of the courses we produced, and it
freezes at the logon screen and won't let her type in her name, password, etc.
We are using AW7.02 and published the course using packaging it with the
Runtime player. The initial background graphic is displayed, along with the
logon screen. However, the screen won't let her type or click on it, and she
has to shut it down using task manager. Any ideas? Settings? Graphics card
issues, etc?

"Hotel Accounting" <webforumsuser@macromedia.com> wrote in message
news:f0qups$pe7$1@forums.macromedia.com...
> We have a customer who is loading one of the courses we produced, and it
> freezes at the logon screen and won't let her type in her name, password,
> etc.
> We are using AW7.02 and published the course using packaging it with the
> Runtime player. The initial background graphic is displayed, along with
> the
> logon screen. However, the screen won't let her type or click on it, and
> she
> has to shut it down using task manager. Any ideas? Settings? Graphics
> card
> issues, etc?

What's the code doing when it freezes? When you run it as an exe on your
computer, do you get the same?

How did you create the logon screen? Does it use a Text Entry Interaction, a
WinCtrl, or did you use a KO?
It is interacting with a database?
What operating system is the customer using? XP? Vista?

--
_______________________

Paul Swanson
Portland, Oregon, USA
_______________________


"Hotel Accounting" <webforumsuser@macromedia.com> wrote in message
news:f0qups$pe7$1@forums.macromedia.com...
> We have a customer who is loading one of the courses we produced, and it
> freezes at the logon screen and won't let her type in her name, password,
etc.
> We are using AW7.02 and published the course using packaging it with the
> Runtime player. The initial background graphic is displayed, along with
the
> logon screen. However, the screen won't let her type or click on it, and
she
> has to shut it down using task manager. Any ideas? Settings? Graphics
card
> issues, etc?
>

We used the standard KO that comes with AW7.02, so the code is going through
the initialize, set records directory, display, first name, mn, ln, user ID and
password process. We did not change the standard Application Knowledge Object
code, other than move the text entry fields down to a different spot on the
screen. We didn't have the same problem using other computers that we have
tried it on. The program worked just as it should on those computers. In the
KO, we did not use a database, but chose to track user responses to a text
file.

Paul: We used the standard Application KO in AW7.02 and checked the logon
screen option. We used the standard program included in that KO without
changing anything. That KO uses text entry. Also, it is not interacting with
a database, it is simply a stand-alone course with the player. She is using
Windows XP Professional. She said that there weren't any IT security issues,
and she was going to take it home with her tonight to try it on a home
computer. We might try eliminating the logon screen code and sending it to her
again to see if that is the problem.

It could be a rights issue, depending on where the text file that tracks
progress is located. Having the user try it on another computer is a good
idea. Did she have Administrator rights on the computer that was presenting
the problem? If not, see if someone can logon to that PC with Admin rights
to see if it hangs at the same place. If it works correctly, that would
pretty much pin it down to the user account, which would likely be a rights
issue.

--
_______________________

Paul Swanson
Portland, Oregon, USA
_______________________


"Hotel Accounting" <webforumsuser@macromedia.com> wrote in message
news:f0r4h6$32o$1@forums.macromedia.com...
> Paul: We used the standard Application KO in AW7.02 and checked the logon
> screen option. We used the standard program included in that KO without
> changing anything. That KO uses text entry. Also, it is not interacting
with
> a database, it is simply a stand-alone course with the player. She is
using
> Windows XP Professional. She said that there weren't any IT security
issues,
> and she was going to take it home with her tonight to try it on a home
> computer. We might try eliminating the logon screen code and sending it
to her
> again to see if that is the problem.
>

The default records setting is relative to the file location, so if you
haven't changed this in the Application KO it might be trying to save a file
to the CD which would explain the screen freezing at that point. Try
changing this setting in the KO, then repackage.

HTH,
Margaret

"Hotel Accounting" <webforumsuser@macromedia.com> wrote in message
news:f0r4h6$32o$1@forums.macromedia.com...
> Paul: We used the standard Application KO in AW7.02 and checked the logon
> screen option. We used the standard program included in that KO without
> changing anything. That KO uses text entry. Also, it is not interacting
with
> a database, it is simply a stand-alone course with the player. She is
using
> Windows XP Professional. She said that there weren't any IT security
issues,
> and she was going to take it home with her tonight to try it on a home
> computer. We might try eliminating the logon screen code and sending it
to her
> again to see if that is the problem.
>

Paul/Margaret/Amy: I will try both of your suggestions. The "rights" idea
makes sense, and I will try that first. I really appreciate your help on this
issue. We tested the program on several other computers yesterday, and it
works great, so it looks like an isolated issue. I also set her up to try our
web-based version that delivers the course over the web. I will let you know
if we solve the problem.

Jim

I have a similar issue where one screen of edit controls are not responding. ie
you cannot click in them or type. And it is only on this one machine and our
client doesn't have another machine to try on. We logged in as her from here
and did not have the problem. She can click on other fields on other screens.
We had a similar issue where someone had changed the Font setting from Normal
to Small (via Display Properties in the OS) and we set it back to Normal and it
was fine. But we can't seem to find the reason for this particular machine not
responding. Any ideas?