How can it claim to be a virtual machine if it won't run software that will run on the system that it is virtualising? On 2 February 2014 20:31, Darron Black wrote: > On 2/2/14, 12:36 PM, Wouter van Ooijen wrote: > > Dwayne Reid schreef op 02-Feb-14 7:12 PM: > >> Generally, I reset a timer every time a new byte comes in. When the > >> timer expires, I consider that to be the end of the packet. > >> > >> That works pretty well for me but in my case, the bytes are fairly > >> close to each other, and the time between packets is much longer than > >> one byte time. This doesn't work if the packets are really close > together. > >> > >> > > And you'll get in trouble when an usb-to-serial converter is used. > > > > Wouter > Yes... or virtual machines. > > I've had to write and maintain kernel-level device drivers that only > exist to properly manage timeouts on otherwise straightforward serial > level protocols. Even those drivers usually won't work when running > software from virtual machines. > > If you're making a product, don't screw it all up with systems > requirements from the 1990s. > > I will avoid any product if I can't run the user software or a > development environment from a virtual machine. There's no excuse for > that these days. > > > Darron > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 __________________________________________ David C Brown 43 Bings Road Whaley Bridge High Peak Phone: 01663 733236 Derbyshire eMail: dcb.home@gmail.com SK23 7ND web: www.bings-knowle.co.uk/dcb --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .