Re: corrupted images

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 40710
interpreted = N
texte = thanks for the tip John, i'll implement something like that in the future for them... as far as uploading - i think they use the automatic mode for the fetch. that one is supposed to figure out what the os/file system of the destination machine is... On Wed, 19 Jun 2002, John Peacock wrote:> Kalin Mintchev wrote: > > thanks... > > the server is a Linux box and the drives are IBMs i don't know the exact > > model of the hdd... > > it is finding all the files - it just doesn't display them all > > correctly... > > i'm searching for some kind of bitmap integrity checking software. not > > much of a luck so far... > > FTP binary vs ASCII transfer mode is likely to be the culprit; some images will > transfer fine in ASCII mode and others require BIN mode (depending on the > presence of whatever the O/S considers a new line character). Make sure your > client is using BIN mode when uploading... > > Even Linux will slow down if there are multi-10k's files in a directory; I have > a small Perl script which we use to move the files into subdirectories, and then > use this: > > [text]jpgpath=[grep > search=^([0-9][0-9])([0-9][0-9][0-9])[0-9X]*&replace=\1/\2/][SKU][/grep][/text] > > to map to the heirarchy of subdirectories. My SKU's just happen to be ISBN's (9 > numbers plus a possible 10th number or an 'X'). The above algorithym seems to > spread our files around more or less equally; you could do first two characters, > next two characters, next three characters, or whatever to try and get an > efficient hashing. > > John > > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: corrupted images (Glenn Busbin 2002)
  2. Re: corrupted images (Kalin Mintchev 2002)
  3. Re: corrupted images (John Peacock 2002)
  4. Re: corrupted images (Kalin Mintchev 2002)
  5. Re: corrupted images (John Peacock 2002)
  6. Re: corrupted images (Kalin Mintchev 2002)
  7. Re: corrupted images (Donovan 2002)
  8. Re: corrupted images (Kalin Mintchev 2002)
  9. Re: corrupted images (Donovan 2002)
  10. Re: corrupted images (Kalin Mintchev 2002)
  11. Re: corrupted images (Stuart Tremain 2002)
  12. Re: corrupted images (Kalin Mintchev 2002)
  13. Re: corrupted images (Stuart Tremain 2002)
  14. OT: corrupted images (Kalin Mintchev 2002)
thanks for the tip John, i'll implement something like that in the future for them... as far as uploading - i think they use the automatic mode for the fetch. that one is supposed to figure out what the os/file system of the destination machine is... On Wed, 19 Jun 2002, John Peacock wrote:> Kalin Mintchev wrote: > > thanks... > > the server is a Linux box and the drives are IBMs i don't know the exact > > model of the hdd... > > it is finding all the files - it just doesn't display them all > > correctly... > > i'm searching for some kind of bitmap integrity checking software. not > > much of a luck so far... > > FTP binary vs ASCII transfer mode is likely to be the culprit; some images will > transfer fine in ASCII mode and others require BIN mode (depending on the > presence of whatever the O/S considers a new line character). Make sure your > client is using BIN mode when uploading... > > Even Linux will slow down if there are multi-10k's files in a directory; I have > a small Perl script which we use to move the files into subdirectories, and then > use this: > > [text]jpgpath=[grep > search=^([0-9][0-9])([0-9][0-9][0-9])[0-9X]*&replace=\1/\2/][SKU][/grep][/text] > > to map to the heirarchy of subdirectories. My SKU's just happen to be ISBN's (9 > numbers plus a possible 10th number or an 'X'). The above algorithym seems to > spread our files around more or less equally; you could do first two characters, > next two characters, next three characters, or whatever to try and get an > efficient hashing. > > John > > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Kalin Mintchev

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

When do we get to request new features? (1999) Re:quit command on NT (1997) Updating fields from different platforms (1998) [WebDNA] Image Magick and Webdna (2009) Currency Conversion (2003) Forbidden CGI Error (1997) Errata: WCS Newbie question (1997) [listfiles] problems (1997) Emailer help....! (1997) Re[2]: Next X hits (1996) PCS Emailer's role ? (1997) Running _every_ page through WebCat ? (1997) Base64 encryption limitations? (1999) Multiple prices (1997) [WebDNA] www.webdna.us store down?? (2012) Re:Hideif / Showif (1998) calender with business days (1998) [WebDNA] WebDNA Health Monitor (2014) extending webcatalog (1997) Getting Emailer to send mail (1997)