Is this a 64bit or 32bit application?

28 views
Skip to first unread message

flee...@gmail.com

unread,
Oct 18, 2007, 4:21:04 AM10/18/07
to VisualWget Help
Hi,

I checked the download requirements and it states: "On Windows XP
VisualWget requires .NET Framework 2.0 (x86, x64) or newer.". Does
this mean that it's a 64bit application or just compatible with x64
systems?

When checking in Windows Task Manager, it doesn't put the "*32" next
to the process: http://www.start64.hu/images/win64/internet/visualwget-2.png
Maybe it's because of .NET FrameWork?
But as soon as I check it under Process Explorer, it states that it's
a 32-bit image: http://fleet.4242.hu/tmp/screenshots/vista/wget/procexp.png

So is it a 32-bit or 64-bit application, and why is it showed a 32-bit
one in Process Explorer and why isn't in Task Manager?

Thanks :)

Khomsan Ph.

unread,
Oct 18, 2007, 11:18:26 AM10/18/07
to VisualWget Help
VisualWget contain managed assemblies that was build using the default
build options. This means that /platform:anycpu is used. The MSDN
documentation state that, on a 64-bit Windows operating system,
executables compiled with the /platform:anycpu will execute on the 64
bit CLR and DLLs compiled with the /platform:anycpu will execute on
the same CLR as the process into which it is being loaded.

So VisualWget can be a 64-bit application (execute on the 64 bit CLR)
on 64-bit Windows operating system. And maybe this is the reason why
Task Manager does not identifies VisualWget as a 32-bit application.
But in Process Explorer, I don't know why.

VisualWget also contain the modified version of Wget executable. This
executable is a native win32 application that was build using MinGW.

flee...@gmail.com

unread,
Oct 19, 2007, 4:56:35 AM10/19/07
to VisualWget Help
Thank you for your reply. According to this, I asked the Process
Explorer guys on their forum if it's a PE bug, I hope they answer.

Thanks again :)

Reply all
Reply to author
Forward
0 new messages