Who knows how expand a file using assembly language?
454676
You can't do it from a set of asm instructions directly. \n\nYou have to link to a library and import the file I/O functions (such as the C-Runtime Library's fopen(), fread(), fwrite(), fclose() functions).\n\nThen in assembly, you just jump to those functions with the appropriate parameters (e.g., the filename string or data to write) pushed on the stack.\n\nIf you want to save yourself some time, consider trying this (for Visual Studio and C/C++):\n\n- Write a simple C/C++ program that opens a file, appends a byte to it (like your example from 3 bytes to 4 bytes) and closes it.\n- Set Visual Studio's linker/compiler settings to "Generate Assembly Listing"\n- Build the program and look for the assembler file (*.s) that has the asm instructions.\n\nRemember to use the CRT (C-Runtime) functions, fopen/fread/fwrite/fclose.\n\nEnjoy.
312630
go to MS-dos and type "mem"\nu will be given all the details.
477320
In the Microsoft .NET framework an assembly is a partially compiled code library for use in deployment, versioning and security. In the Microsoft Windows implementation of .NET, an assembly is a PE (portable executable) file. There are two types, process assemblies (EXE) and library assemblies (DLL). A process assembly represents a process which will use classes defined in library assemblies. In version 1.1 of the CLR classes can only be exported from library assemblies; in version 2.0 this restriction is relaxed. The compiler will have a switch to determine if the assembly is a process or library and will set a flag in the PE file. .NET does not use the extension to determine if the file is a process or library. This means that a library may have either .dll or .exe as its extension.\n\nThe code in an assembly is partially compiled into CIL, which is then fully compiled into machine language at runtime by the CLR.\n\nAn assembly can consist of one or more files. Code files are called modules. An assembly can contain more than one code module and since it is possible to use different languages to create code modules this means that it is technically possible to use several different languages to create an assembly. In practice this rarely happens, principally because Visual Studio only allows developers to create assemblies that consist of a single code module.\n\nThe name of an assembly consists of four parts:\n\n   1. The short name. On Windows this is the name of the PE file without the extension.\n   2. The culture. This is an RFC 1766 identifier of the locale for the assembly. In general, library and process assemblies should be culture neutral, the culture should only be used for satellite assemblies.\n   3. The version. This is a dotted number made up for 4 values — major, minor, build and revision. The version is only used if the assembly has a strong name (see below).\n   4. A public key token. This is a 64-bit hash of the public key which corresponds to the private key used to sign the assembly. A signed assembly is said to have a strong name.\n\nThe public key token is used to make the assembly name unique. Thus, two strong named assemblies can have the same PE file name and yet .NET will recognise them as different assemblies. The Windows file system (FAT32 and NTFS) only recognises the PE filename, so two assemblies with the same PE file name (but different culture, version or public key token) cannot exist in the same Windows folder. To solve this issue .NET introduces something called the GAC (Global Assembly Cache) which is treated as a single folder by the .NET CLR, but is actually implemented using nested NTFS (or FAT32) folders.\n\nTo prevent spoofing attacks, where a cracker would try to pass off their assembly as yours, the assembly is signed with a private key. You keep your private key secret, so a cracker cannot have access to it, and cannot guess the associated public key. Signing the assembly involves taking a hash of important parts of the assembly and then encrypting the hash with the private key. The signed hash is stored in the assembly along with the public key. The public key will decrypt the signed hash. When the CLR loads a strongly named assembly it will generate a hash from the assembly and then compares this with the decrypted hash. If the comparison succeeds then it means that the public key in the file (and hence the public key token) is associated with the private key used to sign the assembly. This will mean that the public key in the assembly is the public key of the assembly publisher and hence a spoofing attack is thwarted.\n\n.NET code access security is based on assemblies and evidence. Evidence can be anything deduced from the assembly, but typically it is created from the source of the assembly — whether the assembly was downloaded from the Internet, an intranet, or installed on the local machine (if the assembly is downloaded from another machine it will be stored in a sandb
1068097
I'll play your silly game! How Do You Clack A File??
658259
WINRAR / WINZIP allows you to self extract a executable..\n\nTry it..\n\nwww.rarlabs.com
1176799
use winrar \nwin rar can compres files for you and split to littel part if compresd files big \nwinrar is free
679105
Have you tried right clicking on the file then use Open With, and try either wordpad or notepad.\nLst is usually a List extension, it may be a simple ascii list, you will not know yet.
791713
Instead of \n-size ${iSize}c\ntry   \n-size +${iSize}c
293992
Use TOBA (see link below)\n\nToba translates Java class files into C source code. This allows the construction of directly executable programs that avoid the overhead of interpretation.
578454
I can do all that, but except for small numbers I wold never bother.\n\nThe "easy" way, such as it is, is to always go through binary on your way from decimal to hex. \nFor the others, list the bits and add/partition.
163236
go to dos prompt.\ntype in "EDIT" then a space then the program name with extension.\nIt will bring up a basic text editor that hopefully will open the file properly.  (works best on INI, BAT, CMD) \nEXE's a re complied differnetly and might not be accessed by user.\n\nTo make your own program for dos, compose a new file, use correct DOS syntax and save it as a "BAT" file. It stands for batch which is translated by DOS.
381554
88 /r MOV  r/m8,r8  move byte register into r/m byte\n89 /r MOV  r/m16,r16 move word redister into r/m word \n8A /r MOV  r8,r/m8  move r/m bute into byte redister\n8B /r MOV  r16,r/m16move r/m word into word register\n\nA4    MOVS m8,m8  move byte \nA5    MOVS m16,m16 move word
163137
if u are looking a way to learn assembly language Randall Hydes 'The Art of Assembly Language' is the best choice.\nThe book is free to download from http://www.cs.ucr.edu/~rhyde/
79899
just get to file in your command prompt and rename\n\nex.if ur filenmae f1.ex1 you can type\n\nren f2.ex2 where f2 and e2 are new filename and extensions respectively,you can use the old ones also.
356292
I don't understand your question.  Do you want to write an assembler in Visual Basic?  This sounds like a homework exercise for school.  Secondly, no one knows just what this SIC is.
373444
You can found assembly language wherever you want to.  Simply write a language and publicly announce it as your own with the moniker "assembly" - but don't be surprised if the real creator of the language comes after you for it.
123220
using an editor\nif you mean using the command line then\nyou have 2 editors vim and nano\nnano is easier, to open file with nano type this\nnano /path/to/file\nto save the file press Ctrl+O then press Enter\nto Quit press Ctrl+X\n\nif you want to know where is the config files\nyou will find it in the /etc dir