Good day -

The office just ported all PCs to W10 and did a "fresh" install of ATE on each station. When i say fresh, i mean the freshest version we support: 6.4.1547.7

Age aside, when the connection dialog opens with the combo box of available connections, there is an odd behaviour of the field being in destruct mode, in addition, typing the first letter will no longer locate the closest match in the dropdown. I have W10 here, same ATE, and the combobox is not in destruct and search feature is active.

Only difference i can see is that they loaded previously saved profile, so they didn't have to reload every connection.

Not a big problem but with dozens of configs, makes it more of a pain to locate Xfinity when only way to locate is to scroll thru the list.

Any ideas as to the new behaviour?

TIA

PS: Oddly this is on ALL PCs not just a few...

I've tried reproducing this using a fresh 6.4.1547.7 ATE on Win10, but without success.

When you say it's destructive, that sounds like the combo box is in edit mode rather than in select-only mode?

That should be related to INFLD type codes, which you can display by hitting ^\ when the dialog first comes up ...

INFLD REV 7.0U [751]
Types: A]134569TkWhsg|G|E|KA||S||E||C||R||||H||]|}|_|m|}]

The ||S is key here. If it was a lower-case ||s, that would be the mode where you could type another value. The only way I can see that getting set is if the EnableNR preference is set in the registry...

Thanks for the reply.

It was odd. I don't have access to the PC at the moment but i will look at your suggestions tomorrow.

Wondering why ATE would even care enough to store this value in the registry? Didn't you just program INFLD straight up to be select mode?

The original idea was to allow certain power users to be able to type in an arbitrary host address to connect with a default set of configuration operations, without having to create and store a permanent configuration. That option has been in hibernation for some time, but I guess we weren't sure whether it might come in handy.

But it would be somewhat mysterious for that option to have gotten turned on in the registry, since (I don't think) the ability is exposed in the user interface.

Let's confirm that really is the situation before deciding how to characterize it and what to do about it.

testing file embed

[img]https://drive.google.com/open?id=10S5gt2A3u9Helld4XJOHyy4YqJjCqNxa[/img]

https://drive.google.com/open?id=10S5gt2A3u9Helld4XJOHyy4YqJjCqNxa

I see your abacus. Is it a veiled comment on the technological direction we're heading?

No but maybe??!!

I don't see the image straight away, i see a broken icon or something... i only see see it if I click on the URL.

Is that what you are seeing? Or do u see the abacus on the post itself?

Sorry, wasn't clear. I had to click on the link.

Offhand I'm not sure why the BBS doesn't fetch the image and display it directly, as it does in the ones I've linked to our forum. It's probably some security-related thing. But don't see that as being a problem - just use the URL button and enter a description along with the link, e.g.

Ok will do.

Can you please share the syntax how you built your link? Don't see how to do that.

Thanks.

Just click on the "Full Reply Form" button below the edit box, then on the "URL" button. It prompts you for the link and for the description. If you prefer to just type it in manually, you can see the syntax by clicking on the edit button above the post with the link in it. Or use the URL option once to reveal the actual code that it inserts.

First and foremost, Shannon said THANK YOU THANK YOU THANK YOU!! Think this was driving her a little batty??

the INFLD value had ||s and EnableNR had a value of 1. So we set it to 0 and all was good.

So not sure what happened here.. perhaps the import operation has some snafu or the file that they used was corrupt.

Thanks for your assistance here. Learn something new every day... right Herman?! Herman? anybody seen Herman? quick... we need some tapioca STAT! :p

Infld capture