[hpsdr] .NET Framework 1.1

[Erik Anderson]

>From my knowedge an .exe is either 32bit or 64bit, it cannot be both (unless
you create two seperate versions of the exe).  When an exe is running, it
can only load .dll's of the same archtecture (32bit or 64bit) as it is.
 Unless someone is using some really-undocumented methods of switching
architectures in the middle of an exe (which I'm not even sure is possible),
the only way for a 32bit exe to use a 64bit dll (or vice versa) is to
somehow wrap the dll in its own seperate exe.

On Mon, Nov 1, 2010 at 11:52 AM, Joe Martin K5SO <k5so at valornet.com> wrote:

> ***** High Performance Software Defined Radio Discussion List *****
>
> On my Win XP x64 OS system (64-bit) any 32-bit program is automatically run
> in x86 mode (32-bit emulation mode).
>
> Is that NOT the case with the newer Win 7 64-bit machines, George?  If Win
> 7 (64-bit) does automatically run 32-bit programs in an emulation mode is
> this discussion not moot as no special program labeling is then required?
>  If Win 7 (64-bit)  doesn't have such an automatic mode then the discussion
> certainly is not moot, of course.
>
> Joe
>
>
>
> On Nov 1, 2010, at 12:38 PM, Joe Martin K5SO wrote:
>
>  ***** High Performance Software Defined Radio Discussion List *****
>>
>> Ahhh!  Okay.  I understand.  Thank you.
>>
>> Joe K5SO
>>
>> On Nov 1, 2010, at 12:34 PM, george byrkit wrote:
>>
>>  Joe,
>>>
>>> The point is this: the app is either unmarked and runs as whichever your
>>> OS
>>> is (32 bit or 64 bit), which CAN work for KISS, because KISS doesn't use
>>> any
>>> C or C++ code (actually it does: libfft, but you can get a 64 bit version
>>> of
>>> libfft), or you mark it as 32 bit (NOT either 32 or 64 bit), because like
>>> PowerSDR, (yours is a variant of PowerSDR), it uses SOME 32 bit code that
>>> is
>>> C or C++, thus ALL the code in the app must be 32 bit!  You CANNOT mix 32
>>> bit and 64 bit code in the same app!
>>>
>>> Now, I have not downloaded your source and examined it for such
>>> dependencies.  But if it's at all close to Bill's code (yes, I know it's
>>> derived from newer, skinned code), it needs to be marked as 32 bit code.
>>>  It
>>> just will NOT work as 64 bit code even when running on a 64 bit system.
>>>
>>> The issue with Bill's version of PowerSDR has to do with all the C and
>>> C++
>>> code that it includes.  That's DTTPSP, the audio code, and some others.
>>> This code is explicitly built as 32 bit (x86) code...
>>>
>>> Vy 73,
>>> George K9TRV
>>>
>>>
>> _______________________________________________
>> HPSDR Discussion List
>> To post msg: hpsdr at openhpsdr.org
>> Subscription help:
>> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>> HPSDR web page: http://openhpsdr.org
>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help:
> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20101101/c4ff1f25/attachment-0004.htm>