Page 1 of 1

Locked thread?

Posted: Thu Sep 13, 2007 10:22 am
by JamesM
I was just wondering why the 'bochs' thread was locked? Was there something offensive in there? It wasn't a flamewar or anything....?

Posted: Thu Sep 13, 2007 10:26 am
by Combuster
I wondered the same thing, mainly because I wanted to correct that backslashes are normally supported by bochs, both on the command line and in .bochsrc...

Posted: Thu Sep 13, 2007 4:06 pm
by bewing
And I was going to add that you can always double every backslash, and it'll work.

Posted: Fri Sep 14, 2007 1:32 am
by JamesM
Combuster: are they? when people complain about bochs errors usually the error message looks like an incorrectly parsed path. The error 'C', for example (from 'C:\bleh\bleh')

EDIT: in case you take it the wrong way, im not implying that you are wrong (ive never used win32 bochs), only showing my general observation! ;)

Posted: Fri Sep 14, 2007 1:52 am
by neon
Combuster: are they? when people complain about bochs errors usually the error message looks like an incorrectly parsed path. The error 'C', for example (from 'C:\bleh\bleh')
On Win32 it should work.

iirc, most other operating systems only support foward slash (/), which is probably where the error comes from. Please correct me if im wrong :)

Posted: Fri Sep 14, 2007 2:08 am
by Combuster
I don't think backslashes will be a problem with any sane user.
My bochs setup on windows eats backslashes normally. I have both precompiled binaries and self-cygwin-compiled binaries and neither showed any issues. On unix, you obviously wouldn't use c:\...\..., so IMO the problem is nonexistant.
(ive never used win32 bochs)
Then, in the future, would you please not post (educated) guesses and making them look like facts?

Posted: Fri Sep 14, 2007 2:43 am
by JamesM
Combuster wrote:
(ive never used win32 bochs)
Then, in the future, would you please not post (educated) guesses and making them look like facts?
Alright, then. I was under the impression that the OP was using cygwin, which obviously emulates a unix-environment. Is cygwin hard-coded to deal with backslashes too then?

Posted: Fri Sep 14, 2007 4:57 pm
by frank
JamesM wrote:
Combuster wrote:
(ive never used win32 bochs)
Then, in the future, would you please not post (educated) guesses and making them look like facts?
Alright, then. I was under the impression that the OP was using cygwin, which obviously emulates a unix-environment. Is cygwin hard-coded to deal with backslashes too then?
Cygwin works fine with backslashes. For example cd C:\ takes you to /cygdrive/c.