Based on the last few messages (and based on nothing else), it would seem the simulator in question simply does not support the concept of polling the LCD for its status. I find that a little strange, especially if the simulator *does* enforce some kind of minimum delay between LCD operations.

If you're stuck on using this simulator, at the very least include some kind of IFDEF structure so that when you assemble the program for simulation you use a fixed delay that works with the simulator but when you assemble the program for operation on real hardware that it uses the status polling.

Polling the status of the LCD is the preferred approach since it increases the probability that the same code will work regardless of the LCD used whereas a fixed delay obviously won't work if you happen to use an LCD that requires a longer delay. Further, polling the status of the LCD guarantees that your program only pauses for the absolute minimum amount of time necessary whereas delay loops are usually "padded" with some extra delay "just in case." So your program ends up waiting around longer than it really needs to.

Regards,
Craig Steiner