You cannot format a volume larger than 32 GB...


The Win2k Installer, and the OS itself can NOT handle anything over 2 (or 4GB -- See the following). I created 3 partitions at work. The third being the largest. Only after happening across a blip on the net, did I find out that I had to use Win98 to format the third (and largest partition).

I just did a quick search. The only thing definite is that the Win2k Format.exe (.com) is FUBAR!
Posted on 2002-09-22 03:46:09 by eet_1024

wicr0s0ft, search this board or M$.com for "PE File Format" - good to hear straight from the source.

Perhaps would be good to tell you (and hutch-- too) that we cannot search on this board for things such "pe format" because of the limit imposed by your site's script :\
Posted on 2002-09-23 14:54:55 by wicr0s0ft

therefore infinity times zero is one?

Posted on 2002-09-23 16:19:12 by peaslee
lol i use 2k and i can format, fdisk my 120 gig at my plesure
Posted on 2002-09-23 16:58:57 by Qages

lol i use 2k and i can format, fdisk my 120 gig at my plesure

Is it FAT32 or NTFS ?

I will put ReiserFS on my Raid0 system... much better than FAT or NTFS ;)
Posted on 2002-09-23 17:27:32 by bazik


therefore infinity times zero is one?


The trick is not to rewrite the equation :)
Posted on 2002-09-24 01:26:10 by eet_1024

The trick is not to rewrite the equation :)

Haha, I love your new signature :)
Posted on 2002-09-24 01:38:34 by bazik

I didn't find any documents about how resources WORK
or what is added to your OBJ file (wich I assume now that is a direcy transcription of the opcodes/values you put on your .asm file) so it can be called and executable file

Here I attache a .zip with some info about resources format.

Is possible to write PE files avoiding some alignments, and you can write
all code in the header, leaving the rest for the imports. Even, you can
write the iat in the header, but the executable only will run in Windows NT.
Posted on 2002-09-24 02:22:46 by n u M I T_o r

Friends don't let friends use NTFS

LOL. I am on a XP system and switched to NTFS recently because i though it was smarter :)
Now, I have no more DOS, and I can't even go back :)
Ahhhhhh ...
Posted on 2002-09-24 07:03:48 by Axial
I have both the NTFS and FAT16 partitions with the MS-DOS 6.22 installed on the second - everything works smooth and nice. :) NTFS access isn't slower than FAT32 on my machine and I like its protection features.
Posted on 2002-09-24 13:33:30 by Tomasz Grysztar
I also find NTFS helpful.
Because I have a lot of crashes.
But, magically, the docs remain there since I'm using NTFS.
Just reinstall, and the things are still there.
Its very robust.
It's sloppy proof.
Posted on 2002-09-25 13:08:23 by slop
I am really going to read all docs that where indicated/posted here. Thanks to all that have posted til now for the cooperation. I appreciate. :)
Posted on 2002-09-26 18:10:09 by wicr0s0ft
I "wrote" a very simple .exe manually.I go to notepad and type 3 characters:
and saved it as *.exe.
When I ran it, a console window appeared and the cursor jumped about madly and the computer alerted me that there was a printing problem.
The printing size kept increasing.(Ought the printing buffer explode!) until I closed the so-called "program".
So it is actually a printing-some-wierd-characters "program".
Posted on 2003-05-09 03:42:00 by chirbyji
Cool! It works with Windows XP too :) (though I don't get the error message)
Posted on 2003-05-09 04:33:10 by Delight
"abc" will be interpreted as a .com file.
The first instruction is popa, the next is incomplete - it will be "completed" with whatever random bytes follow. Since the "program" has no exit, it will execute random code until it crashes (or accidentally hit a dos program termination - like ret, int20, int21/4ch).
Posted on 2003-05-09 04:38:23 by f0dder
Actually the characters:
will just do.
Posted on 2003-05-10 03:51:48 by chirbyji
of course - any file named .exe without a valid MZ header will be interpreted as .com, and you will be executing garbage.
Posted on 2003-05-10 04:53:07 by f0dder
Interestingly enough it is possible to produce programs from only the byte values of readable characters like 'abc'.

There have been a number of tools for converting a .com executable into text -- they all work by encoding the file, and adding a decoder which is cleverly chosen so it also consists of text. I wrote one (c2t) a long time ago -- if anybody should be interested:
Posted on 2003-05-10 08:30:38 by Jibz
0*infinity=2 also
Posted on 2003-05-10 20:28:35 by chirbyji
To reduce the size of output executable you can link the *.obj file with a command line like this:
/ALIGN:4 means that the sections are 4-bytes aligned in the file, instead of 512 default value! so the max padding in the executable will be of 3 zero bytes :-) (note that win95 doesn't support alignments smaller than 512, the program will work only on win NT, 2k, XP)
Another good idea in order to decrease the file size is to merge more sections with similar attributes, this is done via the linker /MERGE switch. Thus you'll avoid a section header too, other 40-bytes :-)
On the PE file format tutorial of Luevelsmeyer there is a very nice example about writing programs by hand. I've tried to do several programs by hand, after a little of experience this operation is merely a copy-paste operation ^_^, dos and pe headers are always that one, with only few changes... resources and directories are more difficult, but you can make your life easier using the same file and section alignment (that is the alignment in the file is the same of that one in memory, when the loader maps the sections into RAM). This let you to avoid converting RVA into offset and vice versa!
I hope you'll find these informations useful :-)
enjoy! :alright:
Posted on 2003-05-11 12:39:47 by Benji