Are you using Java 7 by any chance? I've only seen the msvcr100.dll message with Java 7 (it's been 71 or something like that with earlier versions.) Greenfoot should start up ok anyway though, does it still work properly? If so, then you can safely ignore the error message. It's annoying but doesn't mean anything. If it is Java 7, I believe it's solved for the next release anyway.

I have re installed the latest Greenfoot version (2.1.0) I have installed Java 1.7.0 ()jdk-7-windows-i586.exe) The error is still occurring. I am assuming it is just a case of waiting for the new Greenfoot to be released?

I think you misinterpreted - the problem occurs with Java 7, but should not occur with Java 6. You can either use Java 6, or copy the msvcr100.dll file from the JDK into the directory where Greenfoot is installed, or you can wait for the next Greenfoot release. Also, the error should not stop Greenfoot from starting; if you can put up with it, then there's no need to do anything.

Following on from the above post Whenever I try and start Greenfoot as a limited user it displays the splash screen and just hangs. The C drive is hidden for the users (although I cant see this being a problem with it being installed over the network?) I have also noticed that when looking under the about section in the menu (When logged in as an admin) it has set the log file to be stored on the desktop and I am assuming this is the same for students, which we need to change (if possible) as students do not have write access to the desktop, with it being communal. We would like it to be set to their individual my documents folder if possible. I noticed under the installation instructions it states "We recommend that you copy the demo scenarios from the default location (C:\Greenfoot\scenarios) to a user-specific location for each user (e.g. ...\My Documents\scenarios). Working with scenarios will not work if the folder is write-protected." There my documents are not locally stored, they are redirected via Group Policy to a network drive. Would this affect Greenfoot? The students have full write and read access to their own my documents. I have tried it when installed locally on a machine to see if the network installation was the problem and it still hangs. I cannot see what could be causing the problem Thanks badhamsp

Please send the debug log to the Greenfoot support team. See: http://www.greenfoot.org/programming/support/index.html By "being installed over a network" you mean that Greenfoot is installed on a network share, i.e. a drive other than C:\ ? Then: it depends. Greenfoot needs Java, and Java might be installed on the C:\ drive... It will default to the "greenfoot" folder inside the user's home directory, which is normally the one containing "My Documents". However you can set the home directory by modifying the bluej.userHome property setting in the bluej.defs file (a configuration file which is part of the Greenfoot installation). (The fact that it goes to the desktop when you log in as admin suggests to me that your admin account is misconfigured.) It shouldn't really matter. If students don't have write access to the Greenfoot example projects, then can still open them and "save to" another location, and then open the project at the new location. Davin

Thanks Davin In had planned on copying them to another location, once I could successfully start Greenfoot as a student but I am still trying to establish what is causing it to hang when it gets to the splash screen. Its Greenfoot 2.1.0 with JDK 7 Thanks

I am afraid cant get the debug log when logged in as a student as it just hangs when starting Do you want me to send you the One when I log in as as admin or will this not help? Does Greenfoot need access to any wesbites to run as the students go through a proxy? Is it possible to change where the debug file is saved? How does Greenfoot determine the home directory? Can you please clarify what areas need to have read and write access Thanks

No, the one you get when you log in as admin won't help. No, no access to any websites is required. As I mentioned in a previous post, the debug log is saved in a location which: ... will default to the "greenfoot" folder inside the user's home directory, which is normally the one containing "My Documents". However you can set the home directory by modifying the bluej.userHome property setting in the bluej.defs file (a configuration file which is part of the Greenfoot installation). If you don't specify the home directory via the bluej.userHome setting, the home directory is discovered by checking the "user.home" Java property. To change the home directory location, you need to edit the bluej.defs file which is inside the "lib" folder, which is itself inside the Greenfoot folder. You can open it with Notepad or Wordpad. Find the line which says: #bluej.userHome=/home/mik/tmp Remove the '#', and change it to specify the desired location. Example: bluej.userHome=N:/students Use forward slashes in the location, not backslashes. (N:/students, not N:\students). Write access: Other than for writing the debug log, Greenfoot doesn't need write access anywhere. Read access: Greenfoot must be able to read all the files in the Greenfoot folder (i.e. wherever Greenfoot is installed), and all files in the JDK directory (wherever the JDK is installed). Davin

One thing to check: make sure that the loopback address "127.0.0.1" is listed in the proxy exceptions: - Go to the control panel - choosing "internet options" - going to the "connections" tab - click "LAN Settings..." - click "Advanced..." (within the "Proxy server" box) - in the "Exceptions" box, enter "127.0.0.1". If there are already one or more exceptions, separate them with a semi-colon (";"). - click Ok.

After editing the home directory I have tested it on 2 machines (One with the Latest JDK, version 7 and one with last version 6 update). For an unknown reason it still hangs on the machine with the latest JDK installed, however it works on the machine with last version 6 update. Is this a known problem?

Not as such. There was a problem with Java 7 when the proxy is set and 127.0.0.1 is not added to the proxy exceptions, however in this case Greenfoot gave an error message (after some time) rather than simply hanging. Did you try adding 127.0.0.1 to the proxy exceptions? Were you able to produce a debug log?