> I don't think the use of cp was the problem. I commented > out the waitfor _input_server_whatever in the bootscript > and haiku booted all the way with Tracker and Terminal. No > input worked though (although I could still F12 and do a > "teams" that showed the input_server wasn't running). > > Now I remember I think I had this before - Haiku didn't > like my wireless PS/2 keyboard and mouse, but I think a > spare set I had at uni worked OK. I'll give it a go when > I get back at the weekend. A spare PS/2 keyboard and > serial mouse I have here didn't work either though. OK I'm back at uni now and my spare PS/2 mouse and keyboard don't work either. I tried removing the waitfor line in the bootscript, enabling the syslog in the kernel conf and adding a sync to the end of the bootscript but still /Haiku/var/log is empty when I have a look at it in R5 later. An advantage I have now is supported BeOS networking, so I can grab a current SVN and build my own and do some source-level investigation. If I still get the same issue with a current SVN build put on the partition the proper way with jam then I can discount a lot of the possible problems with the downloaded build and my method of mounting and cp'ing it - so I'll add a bug then if it's still a problem. Simon ----------------------------------------- Email sent from www.virginmedia.com/email Virus-checked using McAfee(R) Software and scanned for spam