Comments on: Calling a 32-bit System Command from a Script in x64 Windows

By: Scottie

Scottie — Wed, 15 Dec 2010 19:44:18 +0000

I explained how I made the executable here:

http://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/

And check your e-mail for the source!

By: Mike Farmwald

Mike Farmwald — Sun, 12 Dec 2010 08:20:41 +0000

Thanks for the note.

I had to add “C:\\Windows” as I was running Ruby from another drive than C.

How do you make the distributable .exe for a ruby program? Also, do you share the source code for the LAN Scanning Tool? I just wrote something similar and was curious.

Thanks.

By: Scottie

Scottie — Tue, 15 Jun 2010 20:41:47 +0000

D’OH! You are absolutely correct. I’ll update the article. Thanks!!

By: kamleong

kamleong — Tue, 15 Jun 2010 16:45:33 +0000

You mentioned that “The 32-bit commands are in the system32 folder, and the 64-bit commands are stored in the SysWOW64 directory. x64 Windows looks in SysWOW64 by default when you call a command line function.”. I read somewhere else that SysWOW64 directory actually stores the 32-bit (instead of 64-bit) binaries. That only exist on a x64 Windows. The system32 folder always stores the “native” binary of the OS.

By: kamleong

kamleong — Tue, 15 Jun 2010 16:28:33 +0000

Thanks for the excellent example and explanation on the Windows\sysnative virtual folder