Yes, it sounds to me that a piece of software is searching for environment configuration files, usually stored in ENVARC: . Simply assigning ENV: to RAM: is a workaround to prevent the requesters from appearing, however it is not the ideal solution.
The original WB3.0/3.1 startup-sequence copies the contents of ENVARC: to RAM:env and assigns it as ENV: . This process consumes memory however, and can be replaced entirely by using the excellent HappyEnv/MountEnv packages.
Cheers,
James
x
