> well because hardware is different and some logic is embedded in jaluino > specific libs. but I understand your point... ;)
I was actually thinking that something should be set up so everything other then the includes could be auto copied into your new sample. That way if I change any important comments or code, your sample will be up to date. > I'm thimking about these lines: > > const bit SD_DELAY_AFTER_WRITE = TRUE > > I'm not I'm doing anhthing with this jaluino_bee.jal lib. could this help in > our case? Can try setting SD_DELAY_AFTER_WRITE = FALSE. If that doesn't work, try putting a large delay between your read & writes. Let me know :) Matt. -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
