[Equest-users] Standard File writing error

[Rob Rosen]

In my experience this is a message about writing to the BDL file, after
eQuest reads the .inp file. It is possible to create an .inp file that has
logical errors, such as a system with no thermal zone or a thermal zone with
no system. But when eQuest tries to process this input and write a BDL file,
the logical errors will stop the process, and that error message will be
generated.
 
Usually you can see the cause of the error in the "ATTN Simulation Messages
For Review" report in the .sim file or by clicking Tools > Check Building
Description.
 
Sometimes the way to find the error is to open the .BDL file with a text
editor and search for the word "error". 
 
Hope this helps,
 
Rob Rosen, LEED AP BD+C
Senior Energy Analyst
Taitem Engineering
110 S. Albany St.
Ithaca, NY 14850
Phone: 607-277-1118 ext 110
Fax: 607-277-2119
www.taitem.com <http://www.taitem.com/> 
ü Please consider the environment before printing this e-mail.

  _____  

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of lawrence
Lile
Sent: Sunday, November 06, 2011 7:21 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Standard File writing error


When I try to simulate building performance in version 3.64, I get "Error: 1
standard file writing errors occurred".  

How do I go about getting around this problem?  There should be no reason I
can think of that the program can't write to disk.  

This does not happen if I start a new project, accept all the defaults, and
simulate it, as a simple test.  

The project in question was opened from a thumb drive, and then "save as" to
the hard drive.  Is there some other secret component that has to be copied
to make this work? 

I'm running windows 7 if that makes any difference.






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20111107/d977896c/attachment-0002.htm>