Jester1167
Premium Subscriber
I believe you can get XP Pro to run 64 bit, Vista sucks
XP 64 sucks.
Vista 64 works way better
I believe you can get XP Pro to run 64 bit, Vista sucks
Only issue I've run into with 64 bit Windows 7 is fleix 7.6, so I run that in XP compatability mode. Everything else works so far, what hardware/software are you going to be using?
Windows 7 has amazing great driver support as is, you can use it free until march.
Without my quad-core processors, 8 gigs ram & 64bit OS, I don't think I could have even set up that job.
I would recommend Win7 as well.
If you want run hassle free use 32bit. If you have time to dick around with compatibility issues you can try 64bit. The minimal benefits of 64bit are just not worth it for me.
I just preordered another 12 copies of Win7 (from 4 different vendors). All were Pro and all were 32 bit.
I’ve always loved being on the cutting-edge of tech, but between Shista and 64bit I’ve pulled back off that. Too much to do to waste time fighting problems that do not exist on rock-solid XP 32bit.
.
I printed 8 large prints for our aquarium yesterday. They were for their interactive displays & it was my second time doing graphics for them, even thought they have been ordering & using lots of print work for longer than I've even had my printer. Needless to say, I considered it an important job to do well. The 4' x 6' panels had lots of text blocks with 1/2" copy.
To get good results on the full coverage photo backgrounds, translucent white fuzzy edged panels behind text, and the text, I exported the client-provided InDesign files to end up as 300 dpi, full size .tiff files. These files were all over half a gig each. Without my quad-core processors, 8 gigs ram & 64bit OS, I don't think I could have even set up that job. As it was, I had to work around the clock Thursday night to keep the job on schedule. I also took a hit on the print time, to keep the quality up & ran my Mimaki at 720x720 unidirectional, for a print time of about 1 hour per print... but damn... they look great!
Probably should have built that file as a pdf or eps, it would have cut down the size tremendously.
I'm not sure if I had that luxury, because I didn't design the file, however I am first to admit I have my familiar routines & end up not learning much about alternatives until I need them.
The files came to me as InDesign files. There were a million things going on, & many of them unfamiliar to me, including the many compound paths, raster effects, and masking methods done in InDesign.
I was able to export as .eps files & open in Illustrator. From there the "bleeds' that the designer set up for me were now hidden, because his crop lines (or whatever they were in InDesign) caused them to convert to a "masking" in Illustrator, which I had to release.
At this point, my usual workflow is to export as RGB .tiff files, because on smaller prints, I've had consistent results printing a single flattened raster image, and feel that combining vector & raster images in Flexi is just adding risks of color irregularities with the vector components, as well as the risk of some vector component getting lost, moved, or improperly layered... so for me, I just avoid those risks when I can, especially when there are a million things going on, and done by someone else. (meaning I wouldn't as easily recognize import errors etc.)
So, anyway, that is why i went the route I usually go... but now that I've confessed my limited understanding of my alternatives, as well as my concerns... I would love to learn how I might have been better able to use smaller files. The .eps files I had halfway through the file preparation were about 4 times smaller.
Would you have used those? Or exported the InDesign file as a .pdf instead?
I thought about separating all my text in Illustrator, along with a keyline for registration, & then creating .tiff files of just the images, which looked fine at 100 dpi. I could have aligned the text in flexi & had smaller files that way, but also some other details to watch out for or attend to. I feared i might end up doing that, but tried the 600 meg files instead & got away with it.