Hi.<br><br>A few times now I've been working on documents containing a number of images to find at some point that some or all the images have been replaced by large red crosses (X).<br><br>There doesn't seem to be any consistent action which seems to trigger this - the last time it happened was just after I had updated my table of contents.<br><br>My images are mostly screen dumps. I'm using Word-97 (Office-97 actually) with service release 1 and NT 4 Workstation with service pack 4. The machine has a Pentium II 200MHz processor with 64Mb RAM. I'm usually running Word with another application (the one I'm getting the screen dumps from). Checking the resources in use I have around 30MB of RAM free with both applications running. Hard disk space is about 200MB free.<br><br>Anyone have the solution to this and ideally the reason it's happening?<br>
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Images replaced by big red crosses in MS-Word
- Thread starter Invicta
- Start date
Delete your temp files (*.tmp and ~*.*) off the C:\ while you have all programs closed, run a scandisk, and restart. If not helpful, save file to new name. Cut screen shots and Paste Special-as picture. See how much less space doc takes up and see if less problems with Xs. <p> <br><a href=mailto:techsupportgirl@home.com>techsupportgirl@home.com</a><br><a href= </a><br>
- Thread starter
- #3
I've had this happen to me, also while working with screen captures. It seems to be a problem in 97 (we had SR 2), not in 2000, as I haven't seen the problem at all there. I believe, at least from my experiences, that it happens when the file gets corrupted in some way. The only two solutions I can give you are:<br><br>1) Redo the images (which is what I've had to do)<br><br>2) Make multiple back ups periodically (document 1.1, document 1.2, document 1.3)<br><br>The second one is the one that I've found has helped the most because I can go back and recover a slightly older version before the file got corrupted.<br><br> <p>Linda Adams<br><a href=mailto:Garridon@aol.com>Garridon@aol.com</a><br><a href= Adams Online</a><br>I'm a professional writer, published internationally.
- Thread starter
- #5
Thanks Linda. I too have had to adopt the two approaches you suggest but isn't it always the case that the problem occurs just BEFORE you save the latest version!<br><br>What I don't understand is that if this is a file corruption (and it certainly seems that way) why is the text that immediately follows the image not damaged in any way and then why is the next image damaged, and so on...<br><br>Maybe the images are stored in a separate part of the document structure and the reference to it has become damaged? I don't know what the file structures are but someone from Microsoft may have the answers.<br><br>ANYONE FROM MICROSOFT OUT THERE?<br>
i've had similar experiences, enough to where we just refer to the condition as "The Dreaded Red X".<br>we've come across when pasting a plethora of Excel graphs into Word. I think it may be due to just a memory shortage where Word can't generate all of the images.<br><br>the saddest part about it is that someone at Microsoft (soon to be Mic, Ros, and Oft thanks to the courts) spent the time to actually program the dreaded red x function in. <p>Brian Famous<br><a href=mailto:bfamous@ncdoi.net>bfamous@ncdoi.net</a><br><a href= > </a><br>
- Thread starter
- #7
When it first happened to me I thought it was just a data access issue where Word was unable to load and display the images as quickly as I was moving through the document, so I waited, and waited... Then I calmed myself by telling myself that it was a memory issue - the images were there but not being displayed. I tried printing a page and to my horror it printed a big red X. <br><br>I've cursed every time it's happened to me ever since because I know it means more work for me and I really dislike redoing the same work when it shouldn't be necessary. I understand that commercial software is going to have bugs at first but Office '97 been around for quite some time now.<br><br>
vbaprogammer
Programmer
This is the Microsoft Knowledge Base site which deals with this problem. They have a workaround.<br><br><A HREF=" TARGET="_new">
- Thread starter
- #9
- Status
Similar threads
- Locked
- Question
- Question