29 August 2006
22 August 2006
18 August 2006
64-bit Mac news
Gizmondo reports possible 64-bit Macs in September
TechDigest Apple rumour of 64-bit CPUs in September
Inquirer reports 64-bit 'Leopard' OS knocks spots of Vista
Digit First looks at Leopard 64-bit support
MacWorld WWDC Apple releases 64-bit Xcode Tools
TechDigest Apple rumour of 64-bit CPUs in September
Inquirer reports 64-bit 'Leopard' OS knocks spots of Vista
Digit First looks at Leopard 64-bit support
MacWorld WWDC Apple releases 64-bit Xcode Tools
31 July 2006
64-bit News
Inquirer Core 2 Duo - Macro-Op fusion does not work in 64-bit mode
dtSearch announces 64-bit beta of dtSearch Engine
eXtremeDB-64 New 64-bit In-Memory Database For Linux
dtSearch announces 64-bit beta of dtSearch Engine
eXtremeDB-64 New 64-bit In-Memory Database For Linux
28 July 2006
27 July 2006
Win64: Compiling ICU 3.4.1
I managed to build ICU version 3.4.1 on 64-bit Windows without too much trouble.
I used Visual Studio.NET 2005 and Windows XP Pro 64-bit and the command prompt :-)
Note: Remember to do a custom install of VS2005 otherwise you do not get the 64-bit compilers & tools installed.
To build ICU for Win64, just unzip the downloaded ICU source code.
Load each .sln (Solution File) into VS2005
You'll be prompted to upgrade it, so upgrade each one to VS2005 format.
Once it's upgraded, activate the Configuration Manager.
In the "Active solution platform:" select from the drop down menu.
In the "New Solution Platform" dialog, choose x64 from the list.
Then save & close the solution. Repeat for all .sln files.
To build it all previously you might have done it from the GUI or cmdline as :
but now you can do this :
to build a 64-bit Windows version.
Links:
ICU downloads
I used Visual Studio.NET 2005 and Windows XP Pro 64-bit and the command prompt :-)
Note: Remember to do a custom install of VS2005 otherwise you do not get the 64-bit compilers & tools installed.
To build ICU for Win64, just unzip the downloaded ICU source code.
Load each .sln (Solution File) into VS2005
You'll be prompted to upgrade it, so upgrade each one to VS2005 format.
Once it's upgraded, activate the Configuration Manager.
In the "Active solution platform:" select
In the "New Solution Platform" dialog, choose x64 from the list.
Then save & close the solution. Repeat for all .sln files.
To build it all previously you might have done it from the GUI or cmdline as :
devenv .\source\allinone\allinone.sln /build "Release" or
devenv .\source\allinone\allinone.sln /build "Release|Win32"
but now you can do this :
devenv .\source\allinone\allinone.sln /build "Release|x64"
to build a 64-bit Windows version.
Links:
ICU downloads
26 July 2006
Debian AMD64
Debian to officially run on AMD64.
When Debian 4.0 comes out, AMD64 port will be official rather than unofficial. This is great news.
News story here : TechWorld news link
When Debian 4.0 comes out, AMD64 port will be official rather than unofficial. This is great news.
News story here : TechWorld news link
15 July 2006
Vista x64 install & SUSE 10.1 64-bit install
Vista x64
It took me over 1 hour to install Vista x64 beta 2 edition. First impressions are that it's very good. It seems slower than WinXP 32-bit, but it is a beta and I would guess that there is quite a bit of debugging code active.
The install process was fairly good & was uneventful. From fresh DVD boot to fully logged in it probably took 1.5 hours.
It installed a new boot loader that was compatible with WinXP 32-bit, so the new boot menu shows Windows and previous windows.
NOTE: It's very important to install Windows in the correct date order. If you have WinXP 32-bit, then install WinXP 64-bit afterwards, then Vista after that. If you install older products after newer products then you will find that they newer ones will no longer boot up.
SUSE 10.1 64-bit
The SUSE install was fairly good also. A few more questions were asked, but it chugged away and took under an hour to install in total.
It installed GRUB and now I can boot SUSE 64-bit, Vista 64-bit, WinXP 32-bit without issue.
Personally, I found that SUSE 10.1 is a far better release than 10.0, at least it is on my hardware.
It took me over 1 hour to install Vista x64 beta 2 edition. First impressions are that it's very good. It seems slower than WinXP 32-bit, but it is a beta and I would guess that there is quite a bit of debugging code active.
The install process was fairly good & was uneventful. From fresh DVD boot to fully logged in it probably took 1.5 hours.
It installed a new boot loader that was compatible with WinXP 32-bit, so the new boot menu shows Windows and previous windows.
NOTE: It's very important to install Windows in the correct date order. If you have WinXP 32-bit, then install WinXP 64-bit afterwards, then Vista after that. If you install older products after newer products then you will find that they newer ones will no longer boot up.
SUSE 10.1 64-bit
The SUSE install was fairly good also. A few more questions were asked, but it chugged away and took under an hour to install in total.
It installed GRUB and now I can boot SUSE 64-bit, Vista 64-bit, WinXP 32-bit without issue.
Personally, I found that SUSE 10.1 is a far better release than 10.0, at least it is on my hardware.
14 July 2006
VMware delivers free server software
The amazing VMware virtualisation server software has been released for free.
It has greatly interested me because it's very stable, fast & fully supports 64-bit hosts & guests. Right now, I'm running it on WinXP 32-bit with WinXP 64-bit guest and GNU/Linux Debian 32-bit guest and GNU/Linux Debian 64-bit guest.
For this to work you do need a certain revision of CPU:
64-bit CPU support discussion
Use this tool to check if CPU is compatible link
Press release
Download
It has greatly interested me because it's very stable, fast & fully supports 64-bit hosts & guests. Right now, I'm running it on WinXP 32-bit with WinXP 64-bit guest and GNU/Linux Debian 32-bit guest and GNU/Linux Debian 64-bit guest.
For this to work you do need a certain revision of CPU:
64-bit CPU support discussion
Use this tool to check if CPU is compatible link
Press release
Download
11 July 2006
More Win64 Apps found
Antivirus program NOD32 now has a Win64 version : eset
CutePDF offers a Win64 version.
Kaspersky Internet Security 6.0 supports (x64) Windows XP 64-bit.
Firefox 64-bit Windows builds
Vector64
Mozilla x64
Neowin Windows 64-bit application list
Software List
CutePDF offers a Win64 version.
Kaspersky Internet Security 6.0 supports (x64) Windows XP 64-bit.
Firefox 64-bit Windows builds
Vector64
Mozilla x64
Neowin Windows 64-bit application list
Software List
07 July 2006
Win64 programming tip
HANDLE
On Windows a HANDLE type is defined as a "void *".
For Win32 (32-bit) and int and long and void * are all 32-bit. This can mean that lots of C and C++ programmers have taken the HANDLE and placed it in a long or an int, or vice versa.
To modify the code, so that it is fully Win32 & Win64 compatible, you should really not interchange HANDLE and int or long. In the Windows 64-bit programming model (LLP) they decided that an int and long are both 32-bit, this is in contrast to the LP64 model used by all other operating systems which has int as 32-bit and long as 64-bit.
But under both LLP and LP64, pointers are 64-bit, so a void * will not fit into a (LP64 32-bit int) or (LLP 32-bit int/long). Beware of this, although the compiler warnings will help out a lot.
Use /Wp64 to enable 64-bit porting warnings when using Visual Studio .NET 2003 or 2005.
Advice on HANDLEs
MS 64-bit help for developers
Microsoft Windows 64-bit types
Microsoft 64-bit tools and tips
On Windows a HANDLE type is defined as a "void *".
For Win32 (32-bit) and int and long and void * are all 32-bit. This can mean that lots of C and C++ programmers have taken the HANDLE and placed it in a long or an int, or vice versa.
To modify the code, so that it is fully Win32 & Win64 compatible, you should really not interchange HANDLE and int or long. In the Windows 64-bit programming model (LLP) they decided that an int and long are both 32-bit, this is in contrast to the LP64 model used by all other operating systems which has int as 32-bit and long as 64-bit.
But under both LLP and LP64, pointers are 64-bit, so a void * will not fit into a (LP64 32-bit int) or (LLP 32-bit int/long). Beware of this, although the compiler warnings will help out a lot.
Use /Wp64 to enable 64-bit porting warnings when using Visual Studio .NET 2003 or 2005.
Advice on HANDLEs
MS 64-bit help for developers
Microsoft Windows 64-bit types
Microsoft 64-bit tools and tips
06 July 2006
02 July 2006
WinXP 64-bit and Win2000 dual boot
Possible incompatibility (not fully verified)
I found that after installing Win2000 on my 64-bit AMD chip (long story about HP PC crashing and losing XP 32-bit), and then installing Windows XP 64-bit, everything seemed to work great. I was able to boot into Windows XP and set it all up.
But after rebooting and trying to start Windows 2000, it blue-screened with a "Stop 0x0000007B" error.
I did notice a lot of web pages describing that the installation order is important because each Windows OS installs itself and it's version of ntldr and ntdetect.com. I just didn't think that it would break Windows 2000.
Previously, I had WinXP 32-bit, then installed WinXP 64-bit, and both ran fine together.
I repaired my Windows 2000 partition by copying back the Win2000 ntdetect.com and ntldr.
I found that after installing Win2000 on my 64-bit AMD chip (long story about HP PC crashing and losing XP 32-bit), and then installing Windows XP 64-bit, everything seemed to work great. I was able to boot into Windows XP and set it all up.
But after rebooting and trying to start Windows 2000, it blue-screened with a "Stop 0x0000007B" error.
I did notice a lot of web pages describing that the installation order is important because each Windows OS installs itself and it's version of ntldr and ntdetect.com. I just didn't think that it would break Windows 2000.
Previously, I had WinXP 32-bit, then installed WinXP 64-bit, and both ran fine together.
I repaired my Windows 2000 partition by copying back the Win2000 ntdetect.com and ntldr.
28 June 2006
03 June 2006
XGL 64-bit Linux
The XGL stuff works well on SuSE 10.1 64-bit.
Firstly, I installed the latest ATI drivers.
Then followed the instructions on this SuSE XGL webpage.
It was very slick and smooth and fun. I won't be using it long term though and have even gone back to the regular X driver for my ATI X700 card.
The problem for me, is that the ATI driver makes the card use it's fan all the time and it gets hot & noisy. Especially when you kick in XGL visual effects, like the spinning cube or fancy window movement.
I'm guessing that all OpenGL type interfaces will do the same thing and cause the card to need to switch on the fan. But it bugs me :-). I've seen it & it works well in 64-bit mode. But I've done back to the quiet driver.
Firstly, I installed the latest ATI drivers.
Then followed the instructions on this SuSE XGL webpage.
It was very slick and smooth and fun. I won't be using it long term though and have even gone back to the regular X driver for my ATI X700 card.
The problem for me, is that the ATI driver makes the card use it's fan all the time and it gets hot & noisy. Especially when you kick in XGL visual effects, like the spinning cube or fancy window movement.
I'm guessing that all OpenGL type interfaces will do the same thing and cause the card to need to switch on the fan. But it bugs me :-). I've seen it & it works well in 64-bit mode. But I've done back to the quiet driver.
26 May 2006
Win64 & Win32 EventLog
I did find that after a hang in Win32, I rebooted into XP 64-bit and then attempted to load EventViewer and load up the 32-bit event logs. Well, it complained about the file format being corrupt.
I've since tried it again today and it worked fine, maybe it was just a glitch.
I've now seen Win32 eventlogs from Win64 and seen Win64 eventlogs from within Win32 :-)
I've since tried it again today and it worked fine, maybe it was just a glitch.
I've now seen Win32 eventlogs from Win64 and seen Win64 eventlogs from within Win32 :-)
25 May 2006
New ATI Linux 64-bit drivers
ATI Proprietary Linux Driver Version 8.25.18 is released.
It now supports X.org v7.0 as well as earlier versions. SuSE 10.1 uses (v6.9.0)
ATI
It now supports X.org v7.0 as well as earlier versions. SuSE 10.1 uses (v6.9.0)
ATI
12 May 2006
OpenSuSE 10.1 First look
I replaced my SuSE 10 64-bit with SuSE 10.1 64-bit yesterday evening.
Noise
The main problem that I had with SuSE 10 was that on my Athlon 64 HP a1130n machine, it always made a lot more noise than when running Windows. WinXP 32-bit & 64-bit were both almost entirely silent, except when really pushing the CPU. Using Linux it made a lot of fan noise just starting up X.
The noise was reduced by running the ATI binary driver. The PC was then far more responsive and far quieter.
Upgrade
Well that problem was been solved with SuSE 10.1. It all felt very slick.
The installation was smooth, much improved since 10.0.
What impressed me the most was the GNOME setup: the theme looks amazing, the layout polished & overall much faster. The Beagle search indexed my /home directory and seems very responsive in searching through thousands of files that I had installed.
I haven't need the ATI driver yet, I noticed that SuSE 10.1 uses X.org 6.9.0 which the binary driver does not yet support. But as of now, I don't need it. X feels so smooth and the PC so fast & silent that I don't need it yet.
I'm very happy with this upgrade, one of the best Linux based OS I've used.
SuSE 10.1
Noise
The main problem that I had with SuSE 10 was that on my Athlon 64 HP a1130n machine, it always made a lot more noise than when running Windows. WinXP 32-bit & 64-bit were both almost entirely silent, except when really pushing the CPU. Using Linux it made a lot of fan noise just starting up X.
The noise was reduced by running the ATI binary driver. The PC was then far more responsive and far quieter.
Upgrade
Well that problem was been solved with SuSE 10.1. It all felt very slick.
The installation was smooth, much improved since 10.0.
What impressed me the most was the GNOME setup: the theme looks amazing, the layout polished & overall much faster. The Beagle search indexed my /home directory and seems very responsive in searching through thousands of files that I had installed.
I haven't need the ATI driver yet, I noticed that SuSE 10.1 uses X.org 6.9.0 which the binary driver does not yet support. But as of now, I don't need it. X feels so smooth and the PC so fast & silent that I don't need it yet.
I'm very happy with this upgrade, one of the best Linux based OS I've used.
SuSE 10.1
11 May 2006
Win64 applications
I now have my HP Athlon64 HP a1130n triple booting Win32, Win64 and SuSE 10 64-bit.
So far I haven't found that many Win64 bit applications.
For drivers I've found :
Motherboard drivers (ATI chipset)
Soundcard drivers (ALC 97)
Graphic card drivers (ATI Radeon)
For applications I've found & installed :
Process Explorer 64-bit (www.sysinternals.com)
Firefox Deer Park 64-bit alpha build
7-Zip x64 link
Seen on the Web :
X-Win64
Unreal 2004 64-bit
SiSoft Sandra for Win64
Good Win64 info. on the Web:
Extended64
AMD64
So far I haven't found that many Win64 bit applications.
For drivers I've found :
Motherboard drivers (ATI chipset)
Soundcard drivers (ALC 97)
Graphic card drivers (ATI Radeon)
For applications I've found & installed :
Process Explorer 64-bit (www.sysinternals.com)
Firefox Deer Park 64-bit alpha build
7-Zip x64 link
Seen on the Web :
X-Win64
Unreal 2004 64-bit
SiSoft Sandra for Win64
Good Win64 info. on the Web:
Extended64
AMD64
Subscribe to:
Posts (Atom)