I hope you mean
librarian=1
You cannot have a space there in the
Fallout2 name. It must at the
root level of the same drive where Fallout 2 is installed, and it must be called Fallout2 not Fallout 2. If you have fallout 2 installed somewhere else like C:\Program Files you still need a C:\Fallout2\dev\proto tree.
I tried adding all the protos to the right folders (check)
I tried having no protos in the folders (check)
What is the "right" folder? What do you have specified for master_patches and critter_patche in mapper2.cfg? If your fallout2.cfg has this:
master_patches=C:\Fallout2\data
critter_patches=C:\Fallout2\data
Then your mapper2.cfg must have the same settings. You should not have to copy protos in this area. If a proto is editied in the mapper, the mapper will automatically create a new proto in the master_patches area.
However, if you want to add NEW protos that did not exist before, you need to copy the proto list from the master. For example, if you want to add new items, you need to copy master.dat\proto\items\items.lst to \fallout2\data\proto\items\items.lst. Same goes for any of the other proto types.
If protos are modified or created by the mapper in \fallout2\data and you subsequently run the fallout2 game, they will usually be deleted by the FO2 engine. They must therefore be set to read-only permission, or put inside a DAT file. However, the mapper cannot edit them if they are read-only, so you have to do some toggling of read/write permissions to switch between mapper and game engine. I usually do a bunch of testing in mapper before even trying with the FO2 engine. And now that there is a new utility that can make a DAT file very easy (
DAT2), I don't bother with read-only permissions, I make a dat file, example:
cd \Fallout2\Data
DAT2 a -r PATCH000.DAT
If you then place that dat file in \Fallout2 the game will use that as its patch file and you don't need to worry about read-only permissions.