While I do not know that much about SSD drives, whether or not they can get fragmented, and I have acknowledged that fragmentation is a sometimes cause, I do need to ask if the SSD drive is the only drive on the machine or the main drive on the machine which houses the operating system? It would also be helpful to know (a) how large the image data file that is giving you problems is, (b) if it contains unflattened layers or not, (c) if your operating system’s pagefile is a dynamic or static pagefile, (d) what image editing program you are using , (e) if the image editing program has a scratch disk of its own, and (f) where that image editing applications scratch disk is located with respect to the hard drive partition and the operating system along with its pagefile. If you have another internal non-SSD hard drive on the computer that houses the operating system or even if you have your operating system located on the SSD drive, you still may be encountering a lack of sufficient free and available hard drive space for the Windows print spool folder despite what what you may think or what might appear to be indicated by Windows. The only file sent during this printing session probably does not come from S3P per se but from your image editing program for starters; it is sent to the Windows print spooler subsystem where it is converted into a print job file and placed in a queue for spooling to the printer. The Windows’ spool folder requires enough free and available storage space on the hard drive partition that the spool folder is located in order to process and store the print job file or to expand into if necessary to process and queue the files. If it does not have said free and available space, it will be unable to process the incoming file and convert it to a print job file, choke and inaccurately process the incoming file and the print job file, or backup and corrupt the print job file. If the spooler fails to delete the temporary print job files from previous sessions for whatever reason, the print spooler folder can get clogged up with orphaned print job files that take up available free and usable hard drive space. On the other hand, if this is not the case, it is also possible that the amount free hard drive space displayed in Windows Explorer or My Computer is less than indicated at the time of actual printing because it has be claimed for use by (a) the Windows pagefile if one is using a dynamic as opposed to a static pagefile, (b) a Photoshop or some other program’s dynamic scratch disk, and/or (c) some program that is running in background and using hard drive resources/storage space on the hard drive partition off and on temporarily at the time that the print spooler needs it. From: Keith Sent: Saturday, May 07, 2011 5:46 PM To: datacolor_group@yahoogroups.com Subject: [datacolor_group] Re: New computer! The drive is an new ssd drive-they don't get fragmented. The only file sent to the printer was from within S3P and was the only program running at the time. And there is well over 50gb of free space available. --- In mailto:datacolor_group%40yahoogroups.com, "Laurie Solomon" <ls1000@...> wrote: > > Although I am not with Datacolor, I would suggest that what you encountered is a typical symptom of what happens when the print spooler in Windows is too small to handle the print job due to the existence of orphaned print job files, running out of disk space on the partition to expand into, or sometimes a badly fragmented hard drive. It has nothing to do with S3P. > > From: Keith > Sent: Saturday, May 07, 2011 12:16 PM > To: mailto:datacolor_group%40yahoogroups.com > Subject: [datacolor_group] Re: New computer! > > > Thank you for the info! Now I have another question. > After made this new profile and making a print(the 16 image example within S3P) & letting it dry, I felt it needed some adjustments and went back into S3P(the next day) to make & save the changes(thus creating a new profile) and went to print the example again. The printer(4800) had paper loaded, ink carts over half full(plenty of ink) and I ran a nozzle check to make sure everything was working prior to printing. I called up the example(thru S3P) and using the new profile I hit the print button. Everything was going well until the printer got to the last half of the last row(the little girl, marilyn monroe, & the 2 B&W images)and it just stoped printing. At first I thought something was amiss with the printer and checked the print cue. At that point I shut down the printer and pulled the paper out and turned off the printer. I started it back up and went into PS & pulled up an image, set up print preferences, picked the new profile(PS handles CM-off in print driver) and proceeded to print. Everything went fine. This is the only time I've had a print stop for no reason. Is this something in the S3P? > Also, is there a way to print a different example test image through S3P? > > --- In mailto:datacolor_group%40yahoogroups.com, David Miller <dm2363@> wrote: > > > > > > On May 5, 2011, at 10:59 PM, Keith wrote: > > > > > As per my original post about a new computer running win7-64, I downloaded the latest S3P driver(4.2.1) and following your recommendations I ran a new set of targets and set up a new profile. My concern is were this profile is stored. Upon completion the Spyder3Print screen came back to report that my new profile would be in C:\windows\SYSTEM32\spool\...... If I'm running 64 bit and the lastest driver is for 32\64 bit, shouldn't the profile be stored in something that doesn't indicate 32 bit? Or is it in the right place that PSCS5 & LR3 will find it? > > > > > > > They're fine, the location above is the "correct" Windows location for profiles > > on your system, whether you're running a 32 or 64-bit system. > > > > Photoshop and Lightroom, and every other application that uses profiles, will > > find them there. (Yes, this is the right place)...:-) > > > > David Miller > > Senior Software Developer, Digital Color Solutions > > Datacolor > > >
Message
Re: [datacolor_group] Re: New computer!
2011-05-08 by Laurie Solomon
Attachments
- No local attachments were found for this message.