Recommended Posts

I've downloaded Win7 Home Premium and Ultimate. Both x64. Download speed on MSDN was about 900-1000 KB/sec, but on Connect, it never got over 600 KB/sec.

It was too late for me to install it. I'll be doing it after work today. I'll be installing Home Premium first since I've got something "Special" do to with it. ;)

Trying to do a clean install of the X64 version. When i get to select partitions etc i get the error "Setup was unable to create a new system partition or locate an existing partition".

I have tried removing all partitions on drive and then creating a new one and formatting also i have tried another drive.

I have the ASUS P5Q Deluxe MB.

Anyone?

Sorry to quote myself, but might help other out as i have fixed the problem.

I booted into Vista and using diskmanager set the drive to active, i also disconnected all USB devices and it installed no problem.

Running hapily no driver issues including my Asus Xonar D2 which i thought might be a problem.

Looking good so far!

i had to donwload that mp3 update MANUALLY, because windows update has an error -8007002

i followed the instructions windows gave to about deleting some files in the WINDOWS\softwaredistrabution folder but it won't let me delete them cause the files are in use, but i did shut WU down?

Any ideas anyone?

You can't delete or rename the softwaredistribution folder without stopping the automatic updates service first...

Sorry, my bad. I mean, for x86 programs to work on x64 :

http://blogs.msdn.com/oldnewthing/archive/...22/9244582.aspx

This also means that it is slower, as it is emulation.

It's been said by many that it's being emulated, but it's actually not.

Take a look at Windows 98, for example. Most of the 32bit DLLs do nothing more than reparse the parameters of the 32bit function into the segmented segment:offset required by 16bit code and thunks from 32bit mode down to 16bit (technically V86 mode, but you get the idea) mode and back again. It works on the exact same principle as the old DOS extenders did except they went the reverse way.

Now, with 32bit programs that are running in Windows x64, the process is basically the same, except it thunks from 64bit long mode down to 32bit protected mode and back. There is no "emulation" involved because the x64 CPU can natively execute x86 code. If you were running 64bit Windows on an Itanium processor and wanted to run 32bit applications, then yes, it would be emulated and be slower.

A flat thunk consists of a DLL (or, if bidirectional compatibility is needed, a pair of DLLs -- one 32-bit and one 16-bit) that is used to translate calls from 32-bit code to 16-bit code. 16- and 32-bit memory addresses work very differently: 16-bit addresses consist of two parts, a pointer to a memory segment, and the offset from the start of that memory segment; whereas a 32bit process memory pointer consists of the absolute address of the memory being accessed. To allow the two dlls to communicate, some intermediate code must be used to translate memory addresses (pointers) between platforms.

The most common usage is in the Win16/Win32 APIs, where thunking is used to convert a 16-bit address into a 32-bit equivalent or vice versa. An early example was that Windows for Workgroups version 3.11 shipped with a 32-bit TCP/IP protocol stack (code-named "Wolverine", this was an early implementation of the TCP/IP stack that would later ship with Windows 95). To allow this stack to operate with 16-bit applications, a version of the 16-bit winsock.dll library was included that simply thunked WinSock calls into the 32-bit stack.

Microsoft later created a mostly-complete thunking layer, called Win32s, which allowed 32-bit Windows applications (written to a specific subset of the Win32 API, hence the "s" in Win32s) to run on top of 16-bit Windows 3.1x. In many ways, Windows 95 was essentially a full-scale expansion of Win32s, because much of the underpinnings of Win95 was still 16-bit.

Similar thunking was required in many cases in OS/2 2.x?while most of the operating system was 32-bit, many parts of the kernel and device drivers were 16-bit for compatibility reasons.

Thunking was used in Windows NT/2000 compatibility subsystems: the OS/2 subsystem allowed 16-bit console-mode OS/2 applications to run on Windows NT (x86 only), and the Windows on Windows (a.k.a. "WoW") subsystem permitted 16-bit Windows applications the same ability. The OS/2 subsystem was dropped after Windows 2000, and the WoW subsystem is not provided in 64-bit versions of Windows. 64-bit versions of Windows provide a similar thunking layer, WOW64, to allow use of 32-bit Windows applications.

Vlited this down from just over 3GB to 1.6GB (X64).

Just installed, working perfectly (Y)

Is the patch out yet for the MP3 issue though? It doesn't seem to be on Windows update? :/

Got it dual booting right now, but if everything runs okay for the next few hours I'll probably switch to main OS. The only game I'm playing right now is FM, and steam seems to work just fine :)

http://www.mydigitallife.info/2009/01/08/f...pdate-download/

Update for Windows 7 Beta (KB961367) (x86)

File Name: update_for_windows_7_beta_x86_kb961367.msu

SHA1: 5D89B057874F5D10A4C90EB2021F23EA9850DEB9

ISO/CRC: C370B735

Update for Windows 7 Beta (KB961367) (x64)

File Name: update_for_windows_7_beta_x64_kb961367.msu

SHA1: 5228F60EDAE124203AC08CCED57539CA0EEB1113

ISO/CRC: 71CB9CBE

It hasn't been released on Windows Update, only for Connect users and Windows 7 beta-testers. You can get the MSU from the site posted.

http://www.mydigitallife.info/2009/01/08/f...pdate-download/

It hasn't been released on Windows Update, only for Connect users and Windows 7 beta-testers. You can get the MSU from the site posted.

Thanks (Y)

The "Latest Forum Activity" on Neowin is borked for me in IE8, anyone else? It just doesn't update.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.