Am noticing a more and more common trend amongst file_id.diz makers, and that is to make the files non standard.
Some groups dont obey all the rules of file_id.diz making. For those wondering I will explain some of the rules hoping that it will make a dent.
1. first line describes all necessary info to know about the file:
- not always do you get a file in dir structure as it was released (usenet/keygenbot/bbs/email)
- there are special programs that scan all your files and index them based on your file_id.diz first lines
2. file should have distinctive disc count
people who are in the scene will nod their heads, but you see, how are you to, in automated way, know how many discs a release spans? in ISO/mp3 world its easy, sfv, but in 0day? Here we have relied on the [xx/yy] count, there are various ways how this works, but the general thing is that the disc count part needs to have somewhere the total of all discs.. Ofcourse if you can put the actual disk number the better..
Oh, and dont bitch that all of this counting is *SO* hard, Laxity made their releaser public (DarkOn3 is god), others too.
3. asci art within 45char width limit
Again, many programs allow you to popup file information for archives by looking into the file_id.diz (ie: any decent Commander clone, CFA tools, BBSes). However as this is supposed to be a quick info, the char limit was put in place.
4. nfo should not be more than 10 lines long
Sometimes to fit a cool gfx a longer nfo is ok, however its supposed to be ONLY art, as again, some of the diz displaying file archiving tools will chop what it will consider useless end of nfo. Think of it this way: the closer to top the line is, the more important it should be, first line containing the name of release, the last containing art.
look at NFOs from old well respected groups (class/core/ucf), and when doing a release please make sure the file_id.diz is normal...
So to finalize:
Make FILE_ID.DIZ using above 4 base rules
dont go out of your way to make nfos that no one can read. Dont make them display art under variant font width, Dont make them HTML,
Now, if you dont make nfos, or dont ever rely on file_id.diz, or dont bother with 100,000 crack archives you need not to respond...
( ps: a quick note on what NFO file should be for those wondering wether NFOs have a standard, there isnt as many specific rules but:
width : best 72chars, up to 80
art: ascii (can be also IBM extended ascii, aka: Terminal font on windows)
it should include:
group quick release info
info on the product
installation/release specific instructions
group default disclaimers
 fixed some nfo vs file_id.diz mixups [/edit]