Locked thread?
Locked thread?
I was just wondering why the 'bochs' thread was locked? Was there something offensive in there? It wasn't a flamewar or anything....?
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!
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!
On Win32 it should work.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')
iirc, most other operating systems only support foward slash (/), which is probably where the error comes from. Please correct me if im wrong
OS Development Series | Wiki | os | ncc
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
char c[2]={"\x90\xC3"};int main(){void(*f)()=(void(__cdecl*)(void))(void*)&c;f();}
-
Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
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.
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.
Then, in the future, would you please not post (educated) guesses and making them look like facts?(ive never used win32 bochs)
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?Combuster wrote:Then, in the future, would you please not post (educated) guesses and making them look like facts?(ive never used win32 bochs)
Cygwin works fine with backslashes. For example cd C:\ takes you to /cygdrive/c.JamesM wrote: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?Combuster wrote:Then, in the future, would you please not post (educated) guesses and making them look like facts?(ive never used win32 bochs)