Authorization
Windows 7 to be Available on October 23 Acer said
On October 23, 2009, Windows 7 will be pre-loaded available for Acer Z5600 PC. Unlike the previous statement of Microsoft, Acer confirmed that the pre-loading plan of Windows 7 is going to be a few months earlier before the beginning of 2010.
Aside from the rumours proclaiming the release of the Original Software will be in the end of 2009, Microsoft officers have officially announced that the launching plan would be carried out much sooner than the timescale of Vista.
Additionally, Acer said that any purchase of Vista-based operating system during 30 days before the launching date will have free upgrade of Microsoft programme.
UK Acer’s Marketing Director, Bobby Watkins, declared that Windows 7 would be available on October 23, 2009. “Customers can purchase a new Z5500 computer with free upgrade facility of this 2007 OS programme during the 30 days before. So that they don’t need to wait for D day” said Watkins to Pocket-lint.
Z5600 PC New all-in-one model is basically released to market in order to compete with Acer’s top rival, Asus Eee that will be launched by the end of September 2009.
Windows XP x64 Terminal Server Patch part 2 (optional)
In part 1 I’ve showed how to get rid of some terminal server restrictions on Windows xp x64. But there are still some problems:
1) You cannot connect to the localhost (127.0.0.1) (but can to 127.a.b.c, where a,b,c in [0..255] (except 127.0.0.0 and 127.255.255.255)).
When you’re connecting to remote server, Remote Desktop Connection (mstsc.exe) checks through mtscax.dll that you’re connecting to your own address, connections are only allowed and you’re in the server mode. If this is not true, the connection is denied, usually with this message:. The logic of checking is the same: call gethostbyname for server name and check if it’s not equal to 127.0.0.1. So, we can use a very simple patch: find and replace 7F 00 00 01 (127.0.0.1) with, for example, some invalid network address, like FF FF FF FF (255.255.255.255).
It’s working for all known version of mstscax.dll (from 5.1 to Windows 7; version 5.0, which is shipped with Windows 2000 server, doesn’t have this restriction at all).
Mstscax.dll Universal Patch
( Read more )
1) You cannot connect to the localhost (127.0.0.1) (but can to 127.a.b.c, where a,b,c in [0..255] (except 127.0.0.0 and 127.255.255.255)).
When you’re connecting to remote server, Remote Desktop Connection (mstsc.exe) checks through mtscax.dll that you’re connecting to your own address, connections are only allowed and you’re in the server mode. If this is not true, the connection is denied, usually with this message:. The logic of checking is the same: call gethostbyname for server name and check if it’s not equal to 127.0.0.1. So, we can use a very simple patch: find and replace 7F 00 00 01 (127.0.0.1) with, for example, some invalid network address, like FF FF FF FF (255.255.255.255).
It’s working for all known version of mstscax.dll (from 5.1 to Windows 7; version 5.0, which is shipped with Windows 2000 server, doesn’t have this restriction at all).
Mstscax.dll Universal Patch
( Read more )
Windows XP 64 Terminal Server patch part 1 (mandatory)
Windows XP X64 shares the same binaries with Windows 2003 X64, but Terminal Server has some restrictions on XP. This article shows you how to get rid of them and is based on cw2k ideas from the original Windows XP Terminal Server patch.
Version 1.1 contains bug#1 fix and is smaller (less bytes are changed).
( Read more )
Version 1.1 contains bug#1 fix and is smaller (less bytes are changed).
( Read more )