#!/bin/bash

    proc=$(/usr/sbin/system_profiler SPHardwareDataType | \
    /usr/bin/awk -F': ' '/Processor Name:/ {print $2}')

    if [ "$(/usr/bin/arch)" == "i386" ]; then
        if [ "$proc" != "Intel Core Duo" ]; then
            /bin/echo $(/usr/bin/arch)-64
        else
            /bin/echo $(/usr/bin/arch)-32
        fi
    else
        /bin/echo $(/usr/bin/arch)
    fi

This script will return i386-32 for intel processors limited to 32 bits, i386-64 for 64-bit capable intel processors, and ppc for non-intel processors.

I've called this script archbits and made it downloadable here.

UPDATE (10/8/08): I discovered a much easier way to accomplish this. The following one-liner will work on ppc or intel boxes and will return 1 if the computer is 64-bit capable or 0 if it is not.

sysctl hw.optional | awk -F': ' '/64/ {print $2}'

This can be done by:
1. Right-clicking on the project in the "Solution Explorer"
2. Select "Properties"
3. In "Properties", Select "Build"
4. In "General" part, Set the "Platform target" as x86.

And if you are creating a Setup or Deployment project, you should set the "TargetPlatform" to x86.
To do this, Select the setup or deployment Project in the Solution Explorer and in the properties window, set the "TargetPlatform" to x86.

On his blog, he states -

Honestly, it took me almost ten days of trial and error to figure out all of the details of doing a remote install and to work out all of the bugs prior to actually attempting it remotely on a production server. I developed this process and simulated the remote install on one of my local machines prior to the actual install. The process is broken into three stages and is fully scripted. You should be able to download the scripts, configure them to meet your environment, and remote install via ssh.

To view this step-by-step guide, please visit his blog by clicking here.

Thanks Jeff!

Pet peeves include: (1) The Microsoft patching progrm auto detects x64 and chooses to install IE x64 when Flash is 32 bit and inoperable with 64 bit browsers; (2) VMWare Workstation disallows installation of 64 bit OS when running on Vista Home x64 (appears to require Vista Business or Ultimate); and (3) the work arounds required to install Oracle XE on Ubuntu x64.

A bright note is how slick VMWare Fusion manages installation on a Mac over VMWare Workstation on Windows or Linux. Perhaps those features will be in the next release.

"Sorry, Windows Live programs cannot be installed on Windows Server, Windows XP Professional x64 Edition, or Windows operating systems earlier than Windows XP Service Pack 2."

or

"Windows Live programs can't be installed on this operating system"

It is not that Windows Live programs "cannot be installed," it is just that the folks at Microsoft who decreed such a thing made a stupid move. That's surprising... Apparently, there is not sufficient application testing on these "unsupported" operating systems, and so they decided not to release it for them period.

Feel free to skip down to the uploaded MSI set up files if you do not want to know the knitty gritties.

On a "compatible" XP SP2 machine, WLInstaller.exe smacks relevant set up files and logs in

C:\Program Files\Common Files\WindowsLiveIntaller\MsiSources

NOTE: WindowsLiveInstaller was (sneakily) made a "protected operating system [folder]" so you would need to change this under Folder Options...View, Show Hidden Files and Uncheck "Hide protected operating system files"

Finally, browse over to the MsiSources folder and voila.

I am surprised there is not more accessibility to these set ups, or at least ease in finding them. Any how, I hope someone benefits from these. Enjoy.

Shared Folder

http://liveinstallers.4shared.com

Direct links:

Windows Live-
Mail (Build 12.0.1606)-
http://www.4shared.com/file/55367964/81c74411/WindowsLiveMail-Install_184E7118-0295-43C4-B72C-1D54AA75AAF7.html

Messenger (Build 8.5.1302.1018)-
http://www.4shared.com/file/55367960/86aa8008/WindowsLiveMessenger-Install_508CE775-4BA4-4748-82DF-FE28DA9F03B0.html

Photo Gallery (Build 12.0.1308.1023)-
http://www.4shared.com/file/55367957/33e34668/WindowsLivePhotoGallery-Install_257E440F-781F-459B-9A68-A0872B80C1D6.html

Writer (Build 12.0.1366.1026)-
http://www.4shared.com/file/55368115/eff1a3ae/WindowsLiveWriter-Install_9176251A-4CC1-4DDB-B343-B487195EB397.html

Sign-In Assistant-
http://www.4shared.com/file/55368117/1ffc282/WindowsLiveSignInAssistant-Install_AFA4E5FD-ED70-4D92-99D0-162FD56DC986.html

Please mirror these if you can.

The next version of windows, windows 7 is expected to be released in Jan 2010, client versions of Windows 7 will ship in both 32-bit and 64-bit. I am more than likely not going to swap to vista anytime soon due to the bad press its been having, I'm more than likely going to wait and see what windows 7 has to offer.

_{Screenshot of Windows 7 Milestone 1 Build 6519}

Right now it just looks like vista as its in early development but I'm looking forward to see what differences there will be in looks, features and reliability. Oh and if you are wondering its named 7 as vista was the 6th version.

Fake or Real?

I am pretty sure the above shots are real but here are some more below that I'm not too sure about, I think there fake but take a look anyway.

Finalmente ha salido la version 11.0 de uno de los distros mas queridos de Linux, me refiero al OpenSuse. Esta nueva version incluye mas de 200 nuevas funciones, un instalador rediseñado que hace de este nuevo Suse algo mucho mas sencillo de instalar, un manejo mas rapido de paquetes gracias a las mejoras del ZYpp, tambien tenemos mejoras en KDE 4, GNOME 2.22, Compiz Fusion y mucho mas.

Si estas interesado en adquirir el Open Suse puedes bajarlo siguiendo este link, desde el cual podras escoger entre 3 tipos de arquitecturas 32 bits, 64 bits y PowerPc, tambien esta disponible el Live CD para que puedas probar el Open Suse antes de instalarlo.

-----------------

Probando nuevos features desde Open Suse

When I ran the service and the service tried to connect to Oracle, I got the following error:

System.IO.FileNotFoundException: Could not load file or assembly 'Oracle.DataAccess, Version=2.102.2.20, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
File name: 'Oracle.DataAccess, Version=2.102.2.20, Culture=neutral, PublicKeyToken=89b483f429c47342'

I checked and found that the correct version of Oracle DataAccess provider was installed on the machine. I suspected that it might be some permissions issue and tried explicitly setting permissions on the Oracle folder. That did not help. I then thought it might be some bad install of Oracle DataAccess provider and re-installed it. I still got the same error mentioned above.

Finally, I found the problem:

When I compiled the service application, I had used the default compilation option, which was to target any CPU.

When 'AnyCPU' is specified for the Target CPU, the service will run in 64 bit mode in a 64 bit OS. I had installed only the 32 bit Oracle DataAccess provider on the machine. The service was running in 64 bit mode and trying to load the 64 bit Oracle DataAccess provider DLL and not finding it.

I re-compiled the application and selected 'X86' for the Target CPU and published it to the server.

Voila!!! No more Oracle errors.

32 bit, 64 bit and the 6 Million Dollar Man

Since the days of Windows 95, computers have been primarily based on a 32-bit operating system. In fact, up ‘til now Vista itself has been shipped in 32-bit format. The new Vista is intended to be bigger, faster, stronger - like Lee Majors, who played Steve Austin, in the Six Million Dollar Man - for those of you who remember that 70's serial.

Why You Should Care

You may be asking, "Why does this matter - how will it affect me?". To you a "bit" is something that belongs in the mouth of a horse, not a technology thing. And as far as Flash goes, he's some comic book hero from by gone days.

Well, here it is, plain as day. The Adobe Flash Player is not 64-bit compatible. Clear as mud, right? It means that Flash based web sites, movies, and tutorials - like ProCare Tutorials - won't run in the new Vista without a little work around.

Download Firefox

The solution, according to Adobe, is to use a 32-bit browser, like Firefox. Then install the Free Flash Player in your new browser. You may want to make it your default browser, otherwise, Internet Explorer will still come up.

1. Download Firefox
2. Install the Flash Player
3. Change Your Default Browser in Vista (optional)

Are you sure this isn't a ProCare thing?

Really and truly, this has nothing to do with ProCare. We are the victim here just like any of the other millions of websites that rely on Flash. This is a compatibility problem between Microsoft's Internet Explorer (which is built into 64 bit Vista) and the Adobe Flash Player. According to Adobe they are "working on Flash Player support for 64-bit platforms".

Happy browsing and until next time, cheers!

-Phil

If you have questions or comments about this article (or suggestions for another article) I'd be pleased to hear from you. Drop me at note at phil@procaresoftware.com.

Download them from these URLs.

Then install them in this order, just by double-clicking them:

http://www.mediafire.com/?jtmicwjyomg -> cnijfilter-common_2.70-3_i386.deb

http://www.mediafire.com/?mzr0rrmtyt3 -> cnijfilter-ip1800series_2.70-3_i386.deb

Then, start any browser and open http://localhost:631 to configure your printers.

For More info check out:

http://www.adobe.com/products/

Common Language Runtime Support

For the sake of this discussion, I’m going to assume some familiarity with the Common Language Runtime (CLR) and .NET development, but will dive into some of the details regarding its support for 32-bit and 64-bit applications. The 2.0 release of the CLR introduced a 64-bit version in addition to the already existing 32-bit version. Along with this, the capability to have your .NET code compiled to target a specific platform was also introduced. For instance, when developing with C# and Visual Basic, the developer can pass in the /platform switch to the compiler with potential values of x86, Itanium, x64, or anycpu with anycpu being the default if the switch is not provided. As you can see, this allows the developer to control exactly what platforms the compiled .NET code can execute on. For executables, what happens is relatively straightforward – x86 compiled executables run in 32-bit mode on all systems (WOW64 on 64-bit operating systems), x64 will only execute on computers that support the AMD64 or EM64T instruction sets, and for executables compiled with anycpu, the application will run as a 64-bit process on 64-bit operating systems and a 32-bit process on 32-bit operating systems. Similarly, .NET class libraries can be loaded by an executable only if they support the platform that the loading executable is running under. Therefore, a 32-bit process cannot load a .NET class library that is compiled as x64 assembly only and a 64-bit process cannot load an assembly that is compiled to be x86 only. However, if the class library is compiled as anycpu, it can be loaded by both 32-bit and 64-bit processes.

You can refer to the articles referenced at the end of this article for more information regarding how to build 64-bit applications using the CLR and the .NET Framework.

CRM 4.0 SDK Assemblies

To determine what platform a specific assembly is compiled to target, you can use the CorFlags.exe tool included with the .NET SDK. Simply running it with the file that you want to examine as a command line argument, you will be able to gather enough information to determine what platforms the targeted file supports. For instance, here’s what the output looks like when running CorFlags.exe on the 32-bit version of Microsoft.Crm.SdkTypeProxy.dll.

The important pieces of information here are the PE and 32BIT values. The breakdown for the various different platform targets and their associated values are as follows:

Based on this chart, we can see that this is indeed the 32-bit version of the Microsoft.Crm.SdkTypeProxy assembly. If we ran the same command on the 64-bit version, we’d see that it is compiled with the anycpu value. I won’t get into the details about why these are compiled as such, but given this information, we can start seeing where the problems might pop up during solution development and when it is appropriate to use the two different sets of CRM 4.0 SDK assemblies.

For more information regarding CorFlags.exe, refer to the link at the end of this post.

CRM 4.0 Solution Development

Now that we have understand of some of the details about how the CLR executes .NET code in 32-bit and 64-bit processes and the differences between the two sets of CRM 4.0 SDK assemblies, let’s talk about what it takes to build a portable solution against the CRM 4.0 SDK. There are several different places where you may write code that links against the SDK assemblies, so let’s walk through each of them.

Plug-ins

Plug-ins could be one of the more challenging ones to get correct given the different factors making up who will actually end up executing the code. If the plug-in is registered to execute synchronously, it will execute in the IIS worker process, if the plug-in is registered to execute asynchronously, its execution will be in the MSCRM Asynchronous service, and if the plug-in is available offline, it will run in the Outlook client hosting process. Depending on the complexity of the CRM topology that your plug-in is running in, the “bitness” of the various processes that will execute your plug-in may be incompatible with each other. In this case, the best solution would be to see if you can compile your plug-in code using the anycpu option as this would allow your plug-in to execute in each of these processes without any changes. If you require your plug-in to be compiled platform specific, then you will need to take into account how the plug-in is going to be registered, the processes that may execute the plug-in, and ensure that your plug-in is compiled in a manner that is consistent with the bitness with which those processes will run. This may, however, limit the portability of your solution and require that you have different plug-in assemblies for the different environments you plan on deploying your plug-ins in.

Custom Workflow Activities

Custom workflow activity assemblies pose many of the same challenges as plug-ins. The one scenario we can rule out is having the custom workflow activity executing in the Outlook client hosting process. However, both the IIS worker process and MSCRM Asynchronous service may load the custom workflow activity assembly at various points in a workflow’s lifetime. Therefore, like plug-ins, if you can compile your custom workflow activity assembly with the anycpu option, you can rely on the CLR and CRM to do the heavy lifting for you. If you need to compile your custom workflow activity assembly to be platform specific, you’ll need to ensure that you are registering a version of the assembly that is compatible with the CRM processes that it will execute in for the environments you want it to have it registered.

SDK Client Applications

This type of solution is the one that developers hit most often as the code is not executing from within CRM, but rather an external process that is reading and writing data from CRM via the SDK. When the code is executing within a CRM process, the CRM setup process will ensure that the correct SDK assemblies are in place to ensure that your solution can execute given the CLR restrictions already discussed. However, when calling the SDK from outside of CRM, your application needs to link to the appropriate SDK assemblies so that they can be loaded into your process. Luckily, this is easy to fix using the two sets of assemblies that are now included in the CRM 4.0 SDK. If we look back at the information we gathered from CorFlags.exe earlier, you’ll remember that the 32-bit SDK assemblies are compiled to target x86 and that 64-bit SDK assemblies are compiled to target anycpu. Given this information, simply linking against the 64-bit SDK assemblies from your client application will do the trick as these can be loaded in both 32-bit processes as well as 64-bit processes. If you are building a SDK client application that is going to execute as a 32-bit process only, then you can use either set of the SDK assemblies without running into any issues.

Putting It All Together

As we’ve discussed, there are two sets of CRM 4.0 SDK assemblies – one for 32-bit and one for 64-bit. This may pose problems at runtime for your code, but with a few simple checks and some configuration when building your code, you can make your solution portable across the various environments where your code may execute. The simplest solution is to build your code using the anycpu so that it can target both 32-bit and 64-bit processes and let the CLR and CRM take care of the rest. Luckily enough, this is the default setting in Visual Studio, so you don’t even need to do anything to add this capability to your solution. Just remember to link against the 64-bit version of the SDK assemblies if you are going to potentially run your anycpu code from outside of CRM. If you do need to compile your code to target a specific platform, then you are going to limit the portability of your solution. In this case, you will need to verify that the platform that your code is compiled to target is the same platform that CRM is going to be executing in when tries to execute your code.

To get the CRM SDK assemblies I’ve referred to, you can download the latest version of the SDK.

Additional Resources:

• /platform Compiler Switch
• 64-bit Applications
• Migrating 32-bit Managed Code to 64-bit
• CorFlags.exe documentation

Cheers,

Nirav Shah

But there are many options on the internet when it comes to a quick registry fix.

Which is the best one? Which registry fix is worth the download? Which registry fix will provide the best results?

In this article, we will review five of the most popular registry cleaners available on the World Wide Web today. It is hoped that you, the reader, will be guided properly on how to choose the best registry fix for your needs.

Registry Fix No. 1: Stompsoft Registry Repair

Stomp is known as the most thorough and most aggressive registry fix in the market today. Where other registry fixers can only diagnose 50 to 70 registry-related errors, Stomp can pinpoint more than 700.

Is this a good thing or a bad thing?

Some say that Stomp merely counts errors in the registry that Windows will auto-correct eventually. Some say that Stomp merely looks for errors in places where files don’t really have a bearing on the processes conducted by the system.

Regardless, Stomp’s aggressiveness wouldn’t hurt, and at the end of the day, it’s still about how well the registry is fixed, and on this, Stomp has a pretty good record.

Registry Fix No. 2: CCleaner

Being a free registry cleaner, CCleaner has built a huge and solid following, with most of its patrons claiming that they have been using this registry fix as soon as it was released almost 5 years ago, and they have never looked for any other reg cleaner since then.

For a free registry fix, CCleaner’s features are simply amazing. CCleaner does things right. It erases the useless and redundant files in the registry, and it never meddles with files that may affect the performance of Windows.

And it is constantly updated! This is something that free registry fixes can seldom afford.

Registry Fix No. 3: Registry Mechanic

Registry Mechanic is likewise a stable registry fix. With the newest update, Version 6.0, Registry Mechanic is now capable of recognizing previously unrecognizable errors, and correcting the same, resulting in a cleaner, better performance for your Windows-based PC.

Many online authorities attest to the integrity of Registry Mechanic, mainly because of the aforementioned stability and consistency of this registry fix. This has created a wave of acclaim for the program, which has been translated to many downloads for the same.

Registry Fix No. 4: Registry First Aid

Speaking of acclaims, if the number of awards is to be used as gauge, then Registry First Aid should top this list.

Registry First Aid is a registry fix that boasts of a seamless cleaning process for your Windows operating system. It promises a stable program that will provide the registry fix you need fast and easy.

Registry Fix No. 5: Registry Medic

Registry Medic’s claim to fame, on the other hand, lies in three things: its amazing user-friendly interface, its powerful scan engine, and its ability to remove and immunize your system from spyware and malware infestation.

Registry medic is indeed more than just a mere registry fix. It aims to be a spyware cure and prevention solution as well, making it one of the top downloads of people who wish to speed up and protect the integrity of their PCs.

Customer of mine is currently going through a migration of their Notes environment to Notes 8.0.1. Of course, as any good customer would do, they want to re-evaluate their infrastructure and consulted with their favorite vendor, IBM. One of the questions that came up was, would it behoove them if they switched from a 32-bit environment to a 64-bit environment in order to maximize performance and efficiency?

So here's the skinny and thanks to my teammate Matt Engstrom and IBM's Techline organization. Windows itself can't use anything more than 4 GB of RAM per instance unless you're running 64-bit Windows. If your organization is running 64-bit Windows, then you can also run 64-bit Domino, and take advantage of configurations that have more than 4 GB of RAM.

64-bit Domino is 100% compatible with both 32-bit Domino (so that you can run mixed server environments) and the Notes client. The only thing to be aware of is that upgrading a 32-bit Domino server to 64-bits will take a little bit longer (maybe a couple of hours) because database indices need to be rebuilt with the 64-bit indexing engine. It's a transparent process that happens automatically - no manual intervention required

Regarding 64-bit vs 32-bit support, the recommendation would be that if the servers are memory constrained then they would probably be better off with 64-bit, but if they are processor constrained then 64-bit probably wouldn't do much for them. For details see: http://www-01.ibm.com/support/docview.wss?uid=swg21296452.

this is your captain speaking, kekeke.. this will be my second post dan gw coba cari kategori pertama buat blog gw ini, abis jiper ngeliat blog ricoh..

ok let's start, diawali oleh pembelian laptop compaq v3802 yang dilakukan pada bulan juni 2008 gw dah niat pingin memaksimalkan pengunaan laptop gw, nah secara yang diinstall pada saat pembelian ialah vista basic home edition sedangkan proc yang digunakan AMD Turion(tm) 64 X2 hmmm..

pada akhirnya setelah ditimbang maka diputuskan klo laptop gw beratnya sekitar 2.4 kg huehehehe... kembali ke laptop maka akhirnya diinstal lah vista ultimate 64 kekeke.. sebenernya sih mo diinstalin Ubuntu tapi apa daya hardisk masih blom mencukupi, apalagi masih dibutuhkan buat nyimpen yang "seger-seger" dari GA2008 hehehe.. hehehe.. jadi intinya apa sih?? oleh karena digunakannya OS 64 bit oleh gw maka disini gw akan membahas kelebihan dari digunakannya aplikasi2 64 bit dan apa keunggulan dari OS 64 bit.

32 bit vs 64 bit

jadi apa sih beda nya? oh ya lupa all of my post is based on my opinion so fell free to give me some comment if there is something wrong, hehehe..

oke kita mulai, salah satu benefit dari menggunakan 64-bit long: memberikan kesempatan untuk processor menembus batasan 4gb memory (<i>padahal laptop gw cuma support max 4gb juga de... </i>) selain itu juga memberikan ruang untuk General purpose register sebanyak 2 kali lipat dibandingkan proc 32-bi t(bayangkan saudara-saudara 2 kali lipat hehehe..) which explains why it is faster than a 32-bit processor/mode dan juga memberikan kemungkinan optimasi aplikasi 64-bit. BTW: Windows Vista 64-bit lebih cepat 10.9 % dibandingkan versi 32-bit, data didapat dari hasil benchmark pake GeekBench.

Tapi perubahan dari 32-bit ke 64-bit membutuhkan modifikasi Operating System yang tidak sedikit untuk dapat menggunakan kelebihan arsitektur yang baru ini. Dan selain itu software juga harus di porting untuk dapat menggunakan fungsi atau kemampuan baru yang lebih baik; sedangkan software yang lebih lama biasanya tetap di support melalui hardware compatibility mode (di mode ini processors baru tetap mensupport instruksi 32-bit sebaik 64-bit version), menggunakan software emulasi, atau implementasi 32-bit processor core didalam 64-bit processor (contonya Itanium processors dari Intel, yang mensertakan x86 processor core untuk menjalankan applikasi 32-bit x86). Oerating systems untuk arsitektur 64-bit  biasanya mensupport applikasi 32-bit dan 64-bit.

64-bit arsitektur memang dapat membuat pekerjaan yang melibatkan data set yang besar dalam appliksi seperti digital vide, komputasi scientific, dan database yang besar menjadi lebih mudah, ada pertimbangan apakah dalam mode kompabilitas dapat lebih cepat  dibandingkan dijalankan dalam sistem 32-bit situ sendiri. Di arsitektur x86-64 (AMD64), sebagian besar operating system dan aplikasi-aplikasi 32-bit dapat berjalan dengan baik menggunakan hardware 64-bit. selain itu kecepatan bukan cuma satu-satunya faktor yang perlu diperhatikan dalam perbandingan processor 32-bit dan 64-bit. Aplikasi seperti multi-tasking, stress testing, dan clustering (untuk high-performance computing), HPC, lebih cocok untuk arsitektur 64-bit makanya IBM, HP and Microsoft banyak mengembangkan penggunaan 64-bit.

64-Bit Sofware Support

Terkadang x86-based 64-bit systems kurang kompatible terhadap software yang dibuat untuk arsitektur 32-bit. Masalah yang umum di temui di Microsoft Windows ialah device driver yang tidak kompatible, walaupun rata-rata software dapat berjalan di 32-bit compatibility mode (atau emulation mode) atau berjalan di 32-bit mode secara native (AMD64), hampir tidak mungkin menjalankan driver menggunakan mode
tersebut. Untungnya hardware/device yang dibuat saat ini sudah memiliki 64-bit driver.

Naahhh, oleh karena itu mungkin salah satu pembahasan di blog gw ini mengenai kesulitan yang saya dapat saat menggunakan 64-bit OS ini dan share informasi atau software 64-bit yang saya temui dalam perjalanan berselancar di dunia maya...

According to Microsoft itself... (more information is available here)

"The main differences between the 32-bit versions of Windows Vista and the 64-bit versions of Windows Vista relate to memory accessibility, memory management, and enhanced security features. The security features that are available in the 64-bit versions of Windows Vista include the following:

•Kernel Patch Protection
•Support for hardware-backed Data Execution Protection (DEP)
•Mandatory driver signing
•Removal of support for 32-bit drivers
•Removal of the 16-bit subsystem

One of the greatest advantages of using a 64-bit version of Windows Vista is the ability to access physical memory (RAM) that is above the 4-gigabyte (GB) range. This physical memory is not addressable by 32-bit versions of Windows Vista.

Depending on the version of Windows Vista that is installed, a 64-bit version of Windows Vista supports from 1 GB of RAM to more than 128 GB of RAM. The ability to address more physical memory lets Windows Vista minimize the time that is required to swap processes in and out of physical memory. Therefore, Windows Vista can manage processes more efficiently. This memory management feature helps improve the overall performance of Windows Vista."

According to Webopedia...

-Users would note a performance increase because a 64-bit CPU can handle more memory and larger files

-most benefits of a 64-bit CPU will go unnoticed without the key components of a 64-bit operating system and 64-bit software and drivers which are able to take advantage of 64-bit processor features

-Benefits of 64-bit processors would be seen with more demanding applications such as video encoding, scientific research, searching massive databases; tasks where being able to load massive amounts of data into the system's memory is required.

]]> http://bewas.wordpress.com/?p=26 Sun, 17 Aug 2008 14:44:33 +0000 Bewas http://bewas.pl.wordpress.com/2008/08/17/gta-iv-juz-wkrotce-na-pc/ Na stronie gtasite.pl znalazłem informację, iż GTA IV jednak będzie wydane na komputery PC.

Treść informacji:

Dzisiejszego pięknego dnia, firma Take Two, dystrybutor serii Grand Theft Auto, powiedział naprawde ciekawą wiadomość, mianowicie to, iż Grand Theft Auto IV zostanie wydane na PC! Nie, to nie jest żart! GTA IV na PC zostanie wydane 18 Listopada 2008 roku w Ameryce, a 21 Listopada w Europie! Tak więc, wszystkie "przepowiednie" się potwierdziły, a teraz pozostaje nam tylko czekać...

Oto wypowiedź Sama Housera, dyrektora Rockstar Games na ten temat:

,,Jesteśmy bardzo podekscytowani wydaniem Grand Theft Auto IV na PC. Cały zespół został dedykowany do stworzenia jednej z najlepszych gier na PC. Gra wygląda bardzo przepięknie, jest super grywalna i nie możemy doczekać się, aby wszyscy mogli w nią zagrać. Zapraszamy niedługo na stronę GTA IV, aby dowiedzieć się więcej!"

Wkrótce potem pokazała się następna, równie ciekawa informacja:

G4TV.com ujawniło okładkę brytyjskiego wydania GTA 4 w wersji na PC.

Oprócz tego mamy kilka nowych informacji.

Z napisu "Games for windows" który umieszczony jest na górze okładki, możemy wywnioskować iż gra będzie obsługiwać technologie 32 oraz 64 bitowe.

Druga informacja to napis "Live" po prawej stronie pudełka, który daje nam do zrozumienia iż multiplayer będzie opierać się o tą samą technologie co wersja na Xbox360. Istnieje także prawdopodobieństwo że gracze zarówno z wersji PC jak i Xbox360 mogli by grać razem i korzystać wspólnie z usługi "Live".

Niestety póki co to są plotki, których Rockstar Games nie zdementował oraz nie potwierdził.

Dalej z niecierpliwością czekamy na chyba najważniejsze info czyli wymagania sprzętowe oraz kiedy ukażą się pre-ordery GTA 4 w Polsce.

Warto się cieszyć z tych informacji, bo:

Po pierwsze - GTA San Andreas stanieje :)

Po drugie - najprawdopobniej (ale nie napewno) będzie można grać na PC przez multipalyera bez instalowania aplikacji firm trzecich

Po trzecie - bo grafika będzie ultrarealistyczna i będzie można zobaczyć wiele szczegółów Liberty City, których nie widziało się w GTA III czy w GTA: LCS na konsole.

Ciekawe, czemu Take Two Interactive i Rockstar Games chcą wypuścić grę w wersji 32x i 64x bitowej...

O wszystkich zmianach będę pisał na moim blogu :)

Så här sitter jag efter ett par dagars försök att komma förbi det steget och får bita i det sura äpplet och installera 32-bitars istället (jag vill installera om för att slippa dumheter som Dell installerat, tex Google desktop etc). Som tur är har folk meddelat att det funkar sisådär med många program som inte är anpassade för 64-bitars-OS, så jag kanske inte förlorar så mycket. I värsta fall är det även så att jag får backa till XP (kanske 64-bit dock) för att kunna köra helikoptersimulatorn (Reflex XTR) och musikprogram (Nuendo). Men det får vi se om en stund när jag installerat klart. Nu har den i alla fall precis gjort sin första omstart under installationen (varför måste Windows starta om så förbannat ofta?).

En roligare sidonotering är att den nätverksdisk på 1 TB som jag köpte begagnad härom veckan snurrar på bra och har fått alla låtar, filmer, foton osv på sig och vi använder hittills ca 20% av dess kapacitet. Trevligt. :)

Omstart 2.

Och nu har jag konfigurerat klart och självklart så har den inte hittat lämpliga drivrutiner för varesig det trådlösa eller det trådade nätverket, så jag har svårt att leta efter uppgraderingar för dem. Den vill visst inte leka med mig. Nåja, försöker man göra sånt som inte är tänkt får man väl skylla sig själv.

På't igen.

I read Chapter 2 "Instruction format" (see volume 2a), and found out something about x86 instruction format. In short, x86 instruction has the following format:

| Prefix(es) | Opcode(s) |
+------------+-----------+
| up to 4    | one-, two-|
| one-byte   | or three- |
| prefixes   | byte op-  |
|            | code      |