well i have.
what you see on the picture is a version which can not scroll through allocated memory.
back then in the year 2004, i had this working after many days of hard work!
but I've lost this revision, all what's survived is an early backup.
it is somehow frustrating.
All I can think of is to restart from zero.
I'm now using VB and seriously thinking about Windows ASM.
maybe I'll try again to start off (it is not supported anymore inside Visual Studio).
(http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/masm.png)
the purpose of the program was to have better control over memory allocation!
should i try to reconstruct the work from the year 2004? certainly it would be possible with some effort...
I usually use this opportunity to rewrite/improve my code and try to make sure it's as compatible as possible.
Also, VB ? :toothy
EDIT: And there's a thread to use asm in Visual Studio.
you maybe know VS2008 can not use any assembly language (at least not directly).
and in VB, there are now Array lists (which sort of, resemble the thing i was working on).
not sure about the performance, but guess, the clock rate increased, for the intend application it won't matter.
so it would be for fun/entertainment only.
Quoteyou maybe know VS2008 can not use any assembly language (at least not directly).
Yes, it can. It comes with MASM.
sorry 32 bit processors are no longer relevant for current sales.
"The inline assembler is built into the compiler, so you don't need a separate assembler such as the Microsoft Macro Assembler (MASM).
"
I assume that you have a different VS,
(http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/th_asm.png) (http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/asm.png)
Quote from: tetsu-jpI assume that you have a different VS
No, you can use inline assembly in Visual C++ 2008 for 32-bit code, you can also use a separate assembler. For 64-bit code, inline assembly is no longer allowed and you must use a separate assembler (if you want to use assembly language). You really don't know what you are talking about.
Quote from: Greg on March 31, 2009, 09:48:43 PM
Quote from: tetsu-jpI assume that you have a different VS
No, you can use inline assembly in Visual C++ 2008 for 32-bit code, you can also use a separate assembler. For 64-bit code, inline assembly is no longer allowed and you must use a separate assembler (if you want to use assembly language). You really don't know what you are talking about.
that's pointless and you know it.
I've no commercial need to maintain this project.
don't deal with information that's obvious (for instance, printed on the screenshot).
MASM would be such an assembler? Was that the purpose to visit the forum?
tell me something that I really want to know: http://www.masm32.com/board/index.php?topic=11147.0
Thank you.
tetsu-jp,
I really don't know what you are trying to say, or ask.
[edit] OK, I read your post at that link. You keep saying "VS2008 does not support assembly anymore at all", and I am saying, yes it does. You can interface MASM and VB, I am much more familiar with interfacing MASM and C/C++ so I can't help you much with that. If all your code is 16-bit DOS code then I think you would be better off re-writing the whole thing. Why not re-write it all in one language, then if you have performance problems consider using MASM (or another assembler). You could re-write the whole thing with MASM, if you wanted to.
I think you did not understand it completely.
Also we could cooperate a little on the forum, NP (no problem).
the situation is, the program was written using MASM, and it is a 32bit WINDOWS program!
not a 16bit DOS program. this should be obvious from the 32bit HEX numbers.
it works fine (by the way), printing, keys, memory etc. is done via Windows.
SO THAT's not the problem.
If you can explain how to interface VC++, 64bits, VS2008, also NP, i can use C++,
it's indeed the first language I've used for VS programming.
there is no special requirement to stick to VB.
just, it can be messy to try hours with options, maybe there is a code example already?
also currently i am thinking to restart the project, rather than to try to resemble the lost code.
If you rely on strange language mix&match you should not upgrade your development machine to a newer VS. But considering your view of Vista and XP I think you'd sacrifice speed and usability very easily, just to get your upgrade fix. Come on now, admit it. :cheekygreen:
tetsu-jp,
If you don't already have Visual C++ 2008, then download Visual C++ 2008 Express Edition here (http://www.microsoft.com/exPress/download/). It comes with 32-bit MASM. Then download the Windows SDK here (http://msdn.microsoft.com/en-us/windows/bb980924.aspx), it includes 64-bit MASM (ml64.exe). Follow the instructions here (http://jenshuebel.wordpress.com/2009/02/12/visual-c-2008-express-edition-and-64-bit-targets/). I got it working on Windows 7 Beta x64.
If you already have Visual Studio 2008 Standard or Professional, it's already set up to do x64 builds, just change the project's properties.
You could also use GoAsm (http://www.jorgon.freeserve.co.uk/), which supports x64. There is a GoAsm sub-forum here.
You could also use Pelle's C (http://www.smorgasbordet.com/pellesc/), which supports x64, and has an assembler called POASM. There is a Pelle's Assembler sub-forum here.
actually the latest 32bit MASM v 9 somthing can be gotten http://www.masm32.com/board/index.php?topic=11111.0
and the MASM64 (and my minimum SDK including semi converted inc's, all 64bit libs and some code examples) http://www.masm32.com/board/index.php?topic=11115.0
also you can create *real VB dll's and also write MASM code directly in the vb IDE and compile it in, info is here
http://www.masm32.com/board/index.php?topic=11103.0
You can get a VB IDE Assembly clone(basically) from here
http://www.easycode.cat/English/index.htm
I recommend GoASM over MASM though for 64bit as it's superior in almost every way, and is similar enough to 32bit masm that it doesn't take long to learn it(took me a night and i've gotten everything converted I wanted to from masm, thanks Donkey answering questions)
tetsu,
If you can do it you are almost always better off rewriting the code as you will get a better end result. In 32 bit you can use inline assembler in VC but Microsoft supply MASM for a good reason. Inline assembler is not properly compatible with the internal compiler optimisation done in VC so particularly using small bits of inline assembler mixed with VC code produces substandard code and lower performance than either pure assembler or optimised VC code.
You are always better off writing assembler code in a seperate module as you code runs as well as you have written it and the VC code is fully optimised by the compiler with no interference with inline assembler register usage. With 64 bit VC you have no choice as the internal compiler optimisation is a lot more complex due to the stack/register techniques used in 64 bit Windows.
thanks a lot.
I've build some inline libraries for 128 bit math in assembly, in the year 2001, using VC++.
(this code is long lost).
Never had any problems interfacing with the compiler made code:
-there have been a few rules on preservation/restore/passing etc.
-there was a disassembler built into the debugger!
back then I had no idea how to do this in C, so i've used 386 assembly.
I have VS Standard edition, VC++, C#, VB, Silverlight, F#.
I think the MASM32 (version 10) is producing 32-bit .OBJ file, can this be linked to 64bit code??
Actually how to interface it properly is a riddle to me, but i will investigate all the links that you have given!
MASM32 programs run, NP, but i guess in x86 IA32 compatibility mode (while the Windows itself runs in 64 bit mode).
but also NP, many softwares are still 32bit.
I have searched the computer for all instances of ML. there is no such program supplied with VS.
neither any version of MASM.
(http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/th_search_ml.png) (http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/search_ml.png)
i guess it is not just 32/64bit, but the technology is entirely different (64 bit is now based on MSIL).
I do not know if it makes sense to install additional express edition (32 bit version), and i do not want to do it, to be honest.
Can you answer it more detailed:
-can MASM32 produce .OBJ file, that can be linked to 64bit project?
BASIC provides keywords to define external DLL/OBJ namespace, i do not know if they can interface 32 bits!
and the data type for windows handle inside VB- 32bits/64 bits? i have no idea!
until i get detailed instructions, I will download everything and try to build interface to VB application.
(I have not read all the AMD manuals but also the standard registers are now different, they are all 64 bits. so at least they must be cleared correctly).
EDIT: I do not think 32bit .OBJ can be linked to 64bit program
EDIT: MFC C++ can be compiled as Win32, ASM can be included. if compiled as x64, error message is generated.
I've tested right now. C++ Windows Forms can not use ASM.
Quote from: tetsu-jp on April 01, 2009, 10:45:51 AM
thanks a lot.
I have searched the computer for all instances of ML. there is no such program supplied with VS.
neither any version of MASM.
Probably because you're using the standard one.
I myself use VS 2008 Team System, and
ml is available
(http://www.stooorage.com/thumbs/78/92696_ml.jpg) (http://www.stooorage.com/show/78/92696_ml.jpg)
tetsu,
The MASM32 Project is 32 bit only, it cannot be used to produce 64 bit modules. If you get the right VC version it has ML64 which can build the 64 bit object modules that will link into a 64 bit C/C++ application. Now interfacing with VB is a different matter, it is not my field but we have members here who have done this type of work.\
The object module format for 64 bit ML64 is not MSIL, it is native 64 bit code that can be linked into other Microsoft native 64 bit code.
as it looks VB can interface to unmanaged DLL.
what you see on the screenshot is wrong code, but generally it can be done that way.
(http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/th_VB_DLL.png) (http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/VB_DLL.png)
all i need to do is to create a DLL (using MASM32)!
how can i do it? HELP!
also i am downloading the WINDOWS SDK (at 1800kbps).
my idea would be to wrap modules iinto 32-bit DLLs, and let the VB application call them, the CPU will run the code in compatibility mode. it is indeed to use a 64bit CPU in 32bit mode, but for many applications, should be OK.
VB can also be switched from x86 to x64 (advanced compiler options).
I've found this for DLL: http://www.jorgon.freeserve.co.uk/TestbugHelp/Dynamic.htm#dll3
should it be possible to create MASM32 DLL only with this resource?
I'd also be able to use WIN32 ASM via C++ (but that's technology which was available ten years ago).
So i want to use the .NET framework via VB, and link ASM code via DLL.
all what's needed is a way to set pixels! and this can be done via GDI+ (which can be provided by .NET framework to VB).
(http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/th_fern_asmcode.png) (http://i25.photobucket.com/albums/c69/nikemoto2511/web200902/fern_asmcode.png)
Quote
all i need to do is to create a DLL (using MASM32)!
how can i do it? HELP!
Not very difficult,but there is some details to know.
Below is a skeletton source file,just add proc in it,that all
Compile it with ml,as others thinks
then link
Quote
\masm32\bin\link /NOLOGO /DEBUG /DLL /DEF:dll.def /SUBSYSTEM:WINDOWS /LIBPATH:\masm32\lib dll.obj
dll.def is a text file that define the name of the dll and the exported function.
sample of contents
LIBRARY skeleton
EXPORTS TestHello
Then you can use the library created by the linker to call the functions or link dynamically (getprocadress) to them.
Quote
.386
.model flat,stdcall
option casemap:none
;--------------------------------------------
; extrait du .def
;LIBRARY skeleton new name for the dll
;EXPORTS TestHello Export of this function
;-------------------------------------------
;Compilation ,assembler normalement,lier une dll
;--------------------------------------------
include \masm32\include\windows.inc
include \masm32\include\user32.inc
include \masm32\include\kernel32.inc
includelib \masm32\lib\user32.lib
includelib \masm32\lib\kernel32.lib
.data
AppName db "DLL Skeleton",0
HelloMsg db "Function of the dll retrieved by GetProcAddress",0
LoadMsg db "The DLL is loaded",0
UnloadMsg db "The DLL is unloaded",0
ThreadCreated db "A thread is created in this process",0
ThreadDestroyed db "A thread is destroyed in this process",0
.code
;le end DllEntry fixe le nom du proc appelé
;pour initialiser la dll
DllEntry proc hInstance:HINSTANCE, reason:DWORD, reserved1:DWORD
.if reason==DLL_PROCESS_ATTACH
invoke MessageBox,NULL,addr LoadMsg,addr AppName,MB_OK
.elseif reason==DLL_PROCESS_DETACH
invoke MessageBox,NULL,addr UnloadMsg,addr AppName,MB_OK
.elseif reason==DLL_THREAD_ATTACH
invoke MessageBox,NULL,addr ThreadCreated,addr AppName,MB_OK
.else ; DLL_THREAD_DETACH
invoke MessageBox,NULL,addr ThreadDestroyed,addr AppName,MB_OK
.endif
mov eax,TRUE
ret
DllEntry Endp
TestHello proc
invoke MessageBox,NULL,addr HelloMsg,addr AppName,MB_OK
ret
TestHello endp
End DllEntry ;
Quote from: tetsu-jpI have searched the computer for all instances of ML. there is no such program supplied with VS.
neither any version of MASM.
Which version of Visual Studio are you using? Visual C++ 2008 SP1 Express Edition, at the link I posted above, includes
ml.exe. The Standard version may not include it, but the Professional and above versions do. They got so many complaints about Express Edition not including it I would think they would have put it in SP1 for Standard too.
there are ML and ML64, in the VC folders.
I have VS2008 Standard Edition, 64bit, with SP1 installed.
Also now i have downloaded the Windows 7 SDK.
I guess the files just did not show up via explorer search.
however, C# and VB directories do not include assemblers.
would the GoASM be a good software to start with 64 bit assembly (eventually use the ML64)?
eventually i want to build for x86, and x64 (the VB program), and then call either 32bit, or 64bit code,
and compare performance.
for now I'd be happy if the 32bit DLL code works!
******************
why the topic "code rot"?
I have lost many projects, over the years, and that's not so good. sometimes I've deleted the stuff myself (and after years, regretted it), sometimes I've lost the computers, and there are cases when I can't maintain the source anymore (for instance, my early RISC ASM sources).
I write differently now, and try to make the sources more readable.
there are certain small C and ASM sources*, for WINUAE emulated machine, better say, I have also lost them,
and after years, ended up with multiple copies of WINUAE at different places, none of them including my source codes!
so it occurs again and again. I am now adding all my sources to SKYDRIVE, and hope they are preserved for the future years.
*years 2004 to 2006.
Quotehowever, C# and VB directories do not include assemblers.
Nope, it only comes with VC.
Quote from: tetsu-jpwould the GoASM be a good software to start with 64 bit assembly (eventually use the ML64)?
Yes, if you are going the assembly only route. Otherwise I would say you should use VC and ML64, they are made to work together.
A suggestion, if you are going to use assembly, forget about VB and C#.
tetsu-jp,
If you have the Masm32 package installed, you will find there a DLL tutorial :
\masm32\tutorial\dlltute
Quote from: Greg on April 01, 2009, 06:53:28 PM
A suggestion, if you are going to use assembly, forget about VB and C#.
1. inline ASM is not supported on x64 platform (only when switching to x86 via compiler option).
forget about VB?
It can call just any DLL, and i could write the DLL in COBOL, FORTRAN, BCPL*, LOGO, etc.
I've read somewhere you are 50 years, and i am the younger person, so i must only write friendly text.
Just, I do not get the content of your statement.I have successfully used inline assembly in C++, but that's not what i want (to use MFC technology).
Also i do not think you experienced problems like me, loosig source codes, so I really don't get it.
*not sure if it can create DLL, it's a hard language
Quote from: Vortex on April 01, 2009, 07:06:11 PM
tetsu-jp,
If you have the Masm32 package installed, you will find there a DLL tutorial :
\masm32\tutorial\dlltute
yes i have found this today, thanks.
5 years ago i managed to write a small program in MASM32, without any guidance...
however it looks some guidance can be helpful.
also I have created the skeletion DLL from the source shown above, and will now try to call it from VB.
tetsu-jp,
It was just a suggestion, you can do whatever you'd like.
Yes, since it is twenty years that i am involved with programming,
I ask how you found such a statement, or why this won't be any good.
One time or the other I'd have my thoughts about OOP and C++ as well.
If i write the subjects that i want to implement, will you write a similar statement?
maybe that it would not make sense, or, "Godd Luck"?
I've got many good-luck wishes for my projects (over the years),
but this never was very productive (for instance, in terms of features).
last not least, do you use modern VB at all?