Anonymous_User Absent Member.
Absent Member.
1175 views

Client 4.9x and Hyper Threading

We're in the process of rolling out 200+ new HP DC7100 desktop systems with
3Ghz P4HT processors using Windows 2000.

Our existing desktops are 600+ Deskpro 1Ghz PIII, which continue to run
without issues.

We've built a new clean image for the new DC7100 using the 4.91 client but
discovered that intermittently, we will see the following error for every
drive that maps in the login script.

"LOGIN-LGNWNT32.DLL-400: A network drive cannot be mapped to a drive that is
designated as a local drive"

We have discovered that we get a reliable fix for this by disabling
Hyper-Threading in the workstation BIOS.

Anyone else had similar problems?

Regards

Pete Griffiths



Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Client 4.9x and Hyper Threading

Interesting bug.

As Windows 2000 doesn't know how to schedule properly on a HT CPU you
should turn it off anyhow.

Out of interest - have you tried replicating it on XP Pro ?

Ian

> We're in the process of rolling out 200+ new HP DC7100 desktop systems

with
> 3Ghz P4HT processors using Windows 2000.
>
> Our existing desktops are 600+ Deskpro 1Ghz PIII, which continue to run
> without issues.
>
> We've built a new clean image for the new DC7100 using the 4.91 client

but
> discovered that intermittently, we will see the following error for

every
> drive that maps in the login script.
>
> "LOGIN-LGNWNT32.DLL-400: A network drive cannot be mapped to a drive

that is
> designated as a local drive"
>
> We have discovered that we get a reliable fix for this by disabling
> Hyper-Threading in the workstation BIOS.
>
> Anyone else had similar problems?
>
> Regards
>
> Pete Griffiths
>
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client 4.9x and Hyper Threading

We now find that the Hyper Threading didn't fix the problem; turning it off
simply made it very much less frequent.

In a further effort to fix the problem we've added the registry keys shown
in the TID's shown below. A couple of our support technicians have been
round classrooms logging in repeatedly over the last three days and we
haven't seen the "LOGIN-LGNWNT32.DLL-400: ..." error since.

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10086186.htm

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10095000.htm

We haven't tried it with XP since we're not planning to migrate from W2K
until 2006. Within our own office we use XP but don't have HT P4 equipped
PC's

Regards

Pete


<ianb@nospam.com> wrote in message
news:i79Me.316$1J2.123@prv-forum2.provo.novell.com...
> Interesting bug.
>
> As Windows 2000 doesn't know how to schedule properly on a HT CPU you
> should turn it off anyhow.
>
> Out of interest - have you tried replicating it on XP Pro ?
>
> Ian
>



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.