[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [K12OSN] Windows XP problem



That hack WILL get a school into serious license trouble with the
Redmond Goon Squad.

If anyone has upgraded an XP machine to SP2 (if you haven't, I know
where a bunch of spam is coming from), dig up the license you "agreed"
to and reread it very carefully. Buried about 2/3 into it is a blurb
about a maximum number of remote connections allowed.

I'm a hard-line staunch advocate of Open Source, GNU Public License,
Linux freedom. It is imperative that ANYONE who wants to see more FLOSS
put into use in schools be also hard-line about being fully paid up on
all required licenses - ESPECIALLY MICROSOFT, ADOBE, APPLE, and all of
the other educational software. That way we can keep the playing field
level and the lawyers out of the schools. Don't go grabbing some cool
hack for Microsoft stuff that lets you do things you _know_ they sell an
upgrade license for. That has already been covered in the license
"agreement" you were strong-armed into accepting. Be adamant about NOT
putting that CD of school software on a second (or 20th) machine when
you KNOW there was only one license purchased. This is how we have to
play the game - fully above board with no "gotcha's" later.

<end soapbox>

On Fri, 2007-12-07 at 13:11 -0600, Doug Simpson wrote:
> Here is a possible. . .
> http://blandname.com/2006/09/19/running-terminal-services-on-windows-xp/
> 
> 
> Doug Simpson
> Technology Specialist
> De Queen Public Schools
> De Queen, AR
> simpsond leopards k12 ar us
> >>> "Doug Simpson" <simpsond leopards k12 ar us> 12/07/07 1:01 PM >>>
> Actually, there is a way to make XP do that with up to 12 clients (no one can login on the main one, though or it acts weird).
> 
> "you cannot do anything to XP to fix this," are you saying "you can't" as in legally or software-ily. . .
> 
> On a Novell network, the main one cannot be logged into. Subsequent connections get their own desktop, run their own login scripts, drive mappings and everything. If a user logs into the main one first, then subsequent connections share the first user's connections. I assume that winders clients would act similarly. . .
> 
> The test computer we were running from was a Winders98 computer and it gave us the XP dexktop, sound, drives and everything. It looked like XP was running right on the terminal, but it wasn't.
> 
> Google for it. It involves a registry key edit and rolling back to an earlier DLL and it will allow up to 12 connections.
> 
> I am not advocating breaking M$ rules here, but it *is* their own software, and it *did* allow it at one time, and it *does* work on the later versions of XP.
> 
> I can't remember the regedit or the dll but google uncovered it . . .
> I'll dig it up if you need it. . .
> 
> Doug
> 
> Doug Simpson
> Technology Specialist
> De Queen Public Schools
> De Queen, AR
> simpsond leopards k12 ar us
> >>> "Kemp, Levi" <lnkemp bolivar k12 mo us> 12/07/07 9:42 AM >>>
> Fajar,
> 
>  You answered your own question here
> "I realized about that WinXP limitation. But the problem occurs when more
> than 4 clients were currently connected."
> you cannot do anything to XP to fix this, the only choice is a Windows Server.
> I do have another question for you though that might help. What applications are needed from windows that cannot be achieved in Linux? You may be able to eliminate the need for windows terminals altogether if you try hard enough.
> 
> Levi Kemp
> Technology Specialist
> Bolivar R-1 Schools
> 417-328-8943
> lnkemp bolivar k12 mo us
> 
> "The only secure computer is one that's unplugged, locked in a safe, and buried 20 feet under the ground in a secret location... and I'm not even too sure about that one"  
> 
> 		--Dennis Hughes, FBI
> 
> 
> 
> -----Original Message-----
> From: k12osn-bounces redhat com on behalf of Fajar Adianto
> Sent: Fri 12/7/2007 8:13 AM
> To: Support list for open source software in schools.
> Subject: Re: [K12OSN] Windows XP problem
>  
> Thanks James,
> 
> I realized about that WinXP limitation. But the problem occurs when more
> than 4 clients were currently connected. Last time it happened when 9
> clients plus 1 on the console. And as I notice, everytime this problem
> happened, there was a line appended in the
> wmiprov.log(windows\system32\wbem\logs\wmiprov.log) read "WDM call
> returned error:
> 4200". Any suggestion?
> 
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
> 
-- 
James P. Kinney III          
CEO & Director of Engineering 
Local Net Solutions,LLC        
770-493-8244                    
http://www.localnetsolutions.com

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney localnetsolutions com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7

Attachment: signature.asc
Description: This is a digitally signed message part


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]