Oh no! I worked so hard on one of my characters and now he's not loading into the scene! The bar goes to 100% then says "An error occurred while reading the file, see log for more details." What do I do? I don't know where the log is, nor do I think it will help me get my character back! Ahhh...I already started over once, it did this before...I was almost done, too!

log.txt is in the DAZ|Studio folder with the application. What happens if you open the scene - does it crash? Or do you get an empty viewport with the things that should be there listed in the Scene palette? If the latter you may be able to save presets (for pose, materials, lights etc.) and quickly rebuild from a freshly loaded base figure. It could also be a memory issue, in which case turning the preview mode to smooth shaded (drop-down list in the title bar, next to the camera picker) may let you load the scene - if possible I'd then split it down, and certainly save presets as above for insurance.

I've had this happen to me as well and it seems to be a memory issue rather than a file corruption issue. I had a moderately complex (for my wimpy computer, that is) scene which gave me the same problem whenever I tried to load it. After multiple tries (and a reboot) I managed to open it up and immediately saved the pose, morph, materials, lighting, and camera presets so I could rebuild the scene rather than struggle with the file every time I wanted to modify it.

Yeah, it seems to be a memory issue. I tried the smooth-shaded thing and I still couldn't load it...weird! I guess all I can do is keep trying? Would it do any good to delete things from my computer (to free up memory) that I don't need anymore? Thanks for the ideas!

No, but it might help to make sure you have as few applications as possible running.

Ok, so this is what the log says:

[i]Opening file coyo2.daz...
Reading coyo2.daz
qWarning: QObject::disconnect: No such signal QObject::projectionChanged()
qWarning: QObject::disconnect: No such signal QObject::projectionChanged()
qWarning: NULL pointer passed to Dz3DViewport::setCamera.
qWarning: NULL pointer passed to Dz3DViewport::setCamera.
qWarning: NULL pointer passed to Dz3DViewport::setCamera.
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Corinthianscori/Vixen/foxears.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Corinthianscori/Vixen/foxearsbump.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Clothing/Boots01texPL.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/Reflection Maps/AKD_Refl_B.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Clothing/Bracer01texPL.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/Reflection Maps/AKD_Refl_A.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Clothing/BootPants01texPL.jpg
File read time: 1 min 19.1 sec.
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Body/APM_Body1.jpg
Error loading file C:/Documents and Settings/Amanda/My Documents/My Pictures/2005-11 (Nov)/coyo2.daz.
File loaded in 1 min 19.6 sec.
Loaded file coyo2.daz.
Unhandled exception: C Exception: Memory Access Violation - Attempted to write memory at address 0xc7396f09. DAZ|Studio must now shut down.
qWarning: QObject::disconnect: No such signal QObject::projectionChanged()
qWarning: QObject::disconnect: No such signal QObject::projectionChanged()
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Body/APM_Body1Bump.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Body/APM_Face1.jpg
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Body/APM_Face1Bump.jpg
*** Scene Cleared ***
qWarning: QObject::disconnect: No such signal QObject::projectionChanged()
qWarning: QObject::disconnect: No such signal QObject::projectionChanged()
Ran tdlmake on image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Body/APM_LashTr.jpg
qWarning: Image C:/Program Files/DAZ/Studio/content/Runtime/textures/Anton'sApolloMaximus/Body/APM_LashTr.jpg not found in the list in DzImageMgr::imagePrepared()
--------------- DAZ|Studio 1.5  Build 1 exited ------------------
~[/i]

So I am pretty sure it's a memory issue. How can I make my computer have more memory? I downloaded a free program called Free Ram XP pro, it's supposed to make more memory available. Worth a try? I've tried opening this now so many times, it's not doing it. LOL.

Maybe increasing virtual memory would help.
It might not; but it can't hurt.

You could try copying the textures elsewhere, for safekeeping, then use an image editor to resample the original texture files to half size and see if the scene will open then.

Dvlenk, how do you increase virtual memory (sorry, not familiar with the technical things, lol).

And RH, I wish I knew what you were talking about! How do you copy the textures elsewhere, and what image editor could I use? I don't know how to go about doing that without being able to open the file. :( I'm lost!

Quote - Dvlenk, how do you increase virtual memory (sorry, not familiar with the technical things, lol).

 
I'm assuming Windows XP?
Control Panel -> System -> Advanced tab -> Performance 'Settings' button -> Advanced tab
Down at the bottom in 'Virtual Memory' section
Press 'Change'. In the pop-up put the radio dial on 'Custom' and turn up the MB number (4096 MB is the limit).
You can set multiple page files (1 page file per hard drive); but, not sure how well that is implemented.
You MUST press the 'Set' Button in the pop up and 'Apply' for the changes to take place. You might have to reboot too; can't remember.

Ok, so how high should I set it? Does it slow down my comp or speed it up? LOL sorry for all the questions, I'm a bit inept...haha, thanks for your help!

4096MB (if you have the 4GB Disk Drive space to spare for it), which you hopefully do. A 32-bit app can't use more than 2 GB, whether it is RAM or Virtual. If you have 2GB RAM free already, then the page file won't help and there is something else wrong.

When you run out of available RAM (or get close to that), it'll write to the file, then use the file as if it were extra RAM. The Virtual memory is slower by far than RAM; but your computer will only use as much virtual memory as it needs to.
If you aren't using any Virtual memory, it won't affect the performance of you machine one way or another. If you start using more memory than you have avail. RAM, then your computer will start to use the virtual memory. The more virtual memory you have to use, the slower your machine will perform.
When you close the program that is using the page file (D|S presumably), then your computer won't need the virtual memory anymore, will stop using it, and go back to normal.

Rhaseltine is talking about resizing the textures to a smaller size so that they require less memory to use (but won't have as good appearance at very close range). i.e if a texture is 2048x2048 make it 1024x1024 and use the smaller image.
He is advising that you make a backup copy of the original, full size, textures images so that if you want to use them at full size, you will have them. I'd second that advice.
You could use any image editor, Paint Shop Pro, Photoshop, GIMP, etc.  Anything really should be able to simply resize.

OK, thanks so much for the help, I'll give it a try!