Some schools suck. Some don't. But all are useful. Even if you don't learn a thing and spend all your time partying, you learn something. College isn't just about book learning. It's about learning about life.
Case in point: me. MIT makes us take 8 humanities classes in order to graduate (among other general requirements which are common across all majors). I got talked into taking a music history class. That class changed my life and opened a whole world of possibilities for me. I'm still a CS major, but I plan to minor (or at least concentrate) in music, all due to this one class that I took more or less because I "had to."
I'm currently taking a writing class (again, one of the core requirements), and it's really opened my eyes to a lot of literature (I highly recommend Moravec for those geeky types).
Sure, I do a lot of learning in my field as well, but if that's all I got, I'd feel a bit cheated. After 2 years here, I can say with confidence that I feel I have grown as a person, and I'm only halfway done.
I don't know japanese or anything, but I do troubleshooting for Athena, and I've run across this problems a few times.
To simply VIEW documents encoded in japanese, just take a file that's encoded with high-bit ascii and open it with netscape, and change the encoding to japanese. I'm not sure where you can pick these fonts up (they are in the standard distribution of Athena).
However, if you want to be able to EDIT japanese files, you'll need to use something like mule (multilanguage emacs), unless you're good with decoding high-bit ascii:)
To print these, look for jlpr, which takes a given input file and converts the high-bit ascii japanese characters to postscript. it's pretty nifty, but I'm not sure it exists outside of MIT's network (not sure if we wrote it).
Your flattery will never work against me, mere mortal! You shall never uncover the coveted secrets of PPC asm environments! mhuahahaha! sleep deprivation kills dammit, i want vi keys in these windows
A few facts about the QWERTY/Dvorak debate
on
The Myth of QWERTY
·
· Score: 1
>One of the main reasons is...
Scientific studies have shown that the most limiting part of typing is being able to translate thought into physical action. The theoretical advantages to Dvorak have not been adequately proven.
I'm sure there is a theoretical maximum, but how that is reached varies. The brain creates what are called "engrams" for frequently used brain pathways. If I spent an entire day practing typing "hxb.,fihnxhb.fkns.huavhk.f,u.", I'm sure I could get VERY good at it, simply because the brain stops thinking "type h. Now type x. Now type b." and thinks, "run that engram for that weird thing." I've noticed that I can type certain key cominations VERY quickly (for example, "edit config.sys", a throwback to my DOS days).
So then the theoretical maximum keyrate becomes proportional to the rate of which nerve impulses travel from your brain to your hands. And we are probably probably NOWHERE NEAR that maxmimum
> FACT: With a QWERTY keyboard, only 30% of your keystrokes will be in the home row.
> FACT: With a Dvorak keyboard, over 70% of your keystrokes will be in the home row.
Again, this does not seem to be the major limiting factor to typing speeds.
It's not...but that's not the point...the point is that it's easier to type, which reduces the number or contorted hand keystrokes that you need to type any given work.
Another advantage with Dvorak is that there are very few words that you can type with one hand (papaya is one example), because the vowels and uncommon consonants are on the left hand, and commond consonants are on the right hand, so most words require switching back and forth between the hands, which is faster. Compare this to QWERTY, which has literally thousands of words that can be typed with one hand (devastate, etc.).
> You can realize for yourself what this means to the average typist.
Nevertheless, it has yet to be proven.
Proof is such a strong word...there can never be a PROOF that one is better than the other, since "better" is subjective. But there is very strong evidence and testimonials from those that have switched. I've never heard of anyone switching from QWERTY to Dvorak and back to QWERTY for any reason besides inconvenience of switching.
> These OSes have a program called xmodmap that makes it simple to switch their keys around.
This doesn't relabel the keys. It doesn't address the fact that no matter what OS you run, you will find yourself at someone else's keyboard.
That's true, but my school has a huge distributed system such that I can access my user account literally anywhere I can access an Athena machine. I work for Athena, my computer is a linux box running redhat/athena, so the only time i need to type in QWERTY is when I'm on someone else's PC running Windows, which is infrequent enough that it's not that much of a hassle. I'll jump back into QWERTY mode after a few minutes (just like riding a bike...). The human brain can be taught to switch back and forth between the two modes relatively easily...it just takes practice.
> As for hotkeys, deal with it. It took me about a week to get used to the new keys in vi--they don't have intuitive positions, but realistically, once you get used to them, it doesn't really matter...
If it doesn't matter where the hot keys are, why does it matter where the other keys are? If the answer is to "get used to it", why bother? Why not "get used to" QWERTY?
if we're going to use that kind of logic, why not place the keys like "ABCDEFGHI..." Because it's really damn hard to type like that. Many programs use hotkeys with two conventions--either make them intuitively named (^C for copy, etc.), or they are placed conveniently (hjkl for vi et al). If it's the former, it doesn't matter where they are. If it's the latter, switching to any non-standard key layout will throw you off.
But it's more than just "getting used to" the position of the keys. I could "get used to" the purely alphabetical layout, but it would be too cumbersome to use (and very painful). Dvorak's key strength is ergonomics.
A few facts about the QWERTY/Dvorak debate
on
The Myth of QWERTY
·
· Score: 3
Dvorak is superior to QWERTY in almost all respects, and the ONLY drawbacks are due to the commonness of the QWERTY layout.
A very interesting article, but flawed. You can't judge the QWERTY/Dvorak debate solely on Economic grounds. Of COURSE it's a pain in the ass to relearn how to type. It can take up to a month before people are up to snuff in Dvorak (it depends on how much you have QWERTY ingrained--i.e., how much you look at the keys, how much you type words instead of letters (that is, you don't think "d-o-g-" when you type, you just think "dog"), etc.).
Dvorak spent over 10 YEARS developing the Dvorak layout, under the guise of a study for the Navy. He filmed typists, found the common problems, and fixed them. I'd like to see ONE study that supports the claim that QWERTY is as fast or faster. It just doesn't make sense:
FACT: Every national typing contest since 1931 has been won by a typist with a Dvorak keyboard.
One of the main reasons is that to execute extremely fast typing (I can do over 150 WPM in QWERTY, no joke), typists form "chords". For examle, to type "the dog" in QWERTY, a fast typist will place his or her fingers over all of the aforementioned keys and then just hit the keys in sequence. This is MUCH easier to do in Dvorak. Here is the Dvorak home row:
A O E U I D H T N S -
So to form a chord for "the dog", you only have to move off the home row for the G. You only move your hands off the home KEYS for the D and G, in fact. This is inherently better than QWERTY. Just watch your hands when you type either. QWERTY is ridiculous.
FACT: With a QWERTY keyboard, only 30% of your keystrokes will be in the home row.
FACT: With a Dvorak keyboard, over 70% of your keystrokes will be in the home row.
You can realize for yourself what this means to the average typist.
There are some disadvantages that others have pointed out. Leaving a keyboard in Dvorak will mess up friends who use your computer. Hotkeys are all messed up. Switching can be a pain in the ass.
But all of these are easily solvable. I run Linux, and I'd guess that a fair number of/. readers use some form of unixish OS. These OSes have a program called xmodmap that makes it simple to switch their keys around. So in my.login, I run "xmodmap $HOME/keyboard/linux.dvorak" (I also have files for Sun and SGI keyboards). This means that others can login to my computer with no problems. The keyboard itself is a QWERTY layout (I love the macro keys on Gateway 2000 keyboards). All the translation is done in software.
As for hotkeys, deal with it. It took me about a week to get used to the new keys in vi--they don't have intuitive positions, but realistically, once you get used to them, it doesn't really matter where the keys are. And if stuff like that really bothers you, hack the programs to change the hotkeys--it's pretty simple.
Switching back and forth will blow your mind the first few times you do it. As it is, I type Dvorak on every computer I log into, but if I am trying to fix something for someone, I will have to type QWERTY more than likely (I haven't managed to convince anyone to switch).
I liken switching from Dvorak to QWERTY to programming in several languages. It doesn't take me 10 seconds to forget everything I know about Perl and start coding in C, and the same goes for the other 10 languages I know--I never get confused, even though several of the languages have similar syntax (Java vs. C++, etc).
But I didn't intend this text to extoll the virtues of Dvorak and beat down the evil QWERTY. It's pretty obvious that Dvorak will stay where it is for some time until there is a sweeping revolution in the keyboard. We can't simply replace the keyboards in our schools with Dvorak because the teachers will refuse. Even if we did, the children who learned to type on these keyboards will only be able to type decently on these keyboards, and will be utterly confused elsewhere. I think the best compromise (at least until QWERTY/Dvorak hardware switchable keyboards are prevalent) is to have everyone learn QWERTY (because it's the most prevalent) *AND* Dvorak.
I suggest that for the other editorals, you give me a copy (through email) so I can weed the grammer and spelling that you didn't quite (not quitte) get right out.
may you have better luck with the spell checker. it's spelled GRAMMAR.
So they were told it was going to be easy. Does that automagically mean that the school is REQUIRED BY LAW to make the class easy? That doesn't make sense.
Whose definiton of easy are we going to use? Ours? Then the university deserves to win. The average non-computer literate person's? Then the students should win.
You simply can't sue for misrepresetation unless there was some legally binding representation of the class.
I don't care how much they paid for the certification class. $1000 or more is nothing...I'm paying $25,000 per YEAR on TUITION here. Should I sue to get my money back because the classes are misrepresented as easy and I have trouble? The fact is that I have trouble in classes that are "easy" here. How is this so? Come to MIT if you want proof that you are not as intelligent as you once thought you were:).
Funny...I've never heard of anything like this before. This has to be the most absurd thing I've ever heard of in my entire life.
Maybe I'm jaded, but filing suit because a class was TOO HARD? About HOW TO USE MICROSOFT APPLICATIONS? I'm too disgusted to even laugh. I'd like to show these 12 morons my 6.002 (Electronic Circuits for non-MIT types) final exam from last term.
I wish I would have known that the prerequisites must encompass EVERY skill I need in a class. Hell, my discrete math class assumes I know how to add, but I didn't see that in the prereqs...they must be misleading me! Where's my lawyer?!
I can't even think of some twisted way to justify this suit. What I suspect is that these 12 slackers all took the class assuming it would be an easy one, and in true slacker form did not keep up with the work and hence failed. Very sad.
They failed the class. Obviously the class was either too difficult for them or they were too lazy. I can't begin to imagine how a class on M$ products would be too difficult for the average (hell, even far below average) college student to comprehend, so the only logical explanation is that they were lazy and it got them in the end.
I really hope they lose and the college files a countersuit. I have no respect for these people or for their lawyer. I'm not sure which is worse--laziness or greed.
The very fact that Gates mentions the fact that "Linux is not a threat" means that he already considers Linux a threat. The momentum has been building for the past few years.
I must admit that until very recently, I was running NT4/NT5/98. Not that I have anything against Linux, I just wanted to play games and game support for Linux, sadly, sucks. That should change soon when Q3A and a few other games are released commercially for Linux (maybe that will kick NVidia into realeasing drivers for their card and I won't have to reboot to play games at all). The reason I switched is that games became unimportant to me (relative to grades at least) and Linux has more functionality outside of games that Windows ever has (you wouldn't believe the amount of software available to me on MIT's distributed system, Athena).
Even though I only installed Linux a few months ago, I have been using UNIX since 1990 or so, and I toyed with Linux on my family's 486/33...I know countless Linux users that will never experience the joy of downloading the ~ 20 slackware disks on a 14.4 modem from sunsite, creating the dreaded root and boot disks (make sure they don't have a single bad sector before you RAWRITE them, or you'll ruin the disk!), etc. Linux is where it is today because there has been a push to make it more user-friendly...even in my day you had a color boot disk and the ability of UMSDOS, both of which made the transition from a DOS environment to Linux a bit easier)
So Linux has made definite progress in the five or so years that I've been using it. There is no reason to think that it will stop or even slow down. I doubt Gates loses sleep over Linux right now, but the fact that Linux is free and there are free alternatives to all of M$'s applications has got to at least make him sweat when these same applications get media coverage (for free, no less).
Pretty nice, but how about a similar FREE product?
on
VMWare Beta Release
·
· Score: 1
Bochs is similar in concept to this...an x86 emulator. One cool thing about Bochs is that it doesn't use any assembly code, so you can compile it on pretty much anything (I think i'll try it out on the UltraSparcs on campus some time). But that also means it's kind of slow (okay, a lot slow). Buuuut, "they" are working on dynamic translation, and premliminary tests show an increase in speed of several orders of magnitude (and that's just optimizing three instructions!). One other cool thing that i've noticed with bochs is that you can use your own VGA and BIOS ROM images...woowoo.
VMWare *almost* boots my windows partition...it passes the bios screen and all that, but when LILO tries to load (i use lilo on the MBR of/dev/hda, which has only windows installed), I get:
L 01 01 01 01...
ad nauseum. I can't quite remember what that number means....does anyone know how to fix this, or at least get around it so i can boot from my DOS partition?
Slashdot Mirror
Case in point: me. MIT makes us take 8 humanities classes in order to graduate (among other general requirements which are common across all majors). I got talked into taking a music history class. That class changed my life and opened a whole world of possibilities for me. I'm still a CS major, but I plan to minor (or at least concentrate) in music, all due to this one class that I took more or less because I "had to."
I'm currently taking a writing class (again, one of the core requirements), and it's really opened my eyes to a lot of literature (I highly recommend Moravec for those geeky types).
Sure, I do a lot of learning in my field as well, but if that's all I got, I'd feel a bit cheated. After 2 years here, I can say with confidence that I feel I have grown as a person, and I'm only halfway done.
Here are some other funny hacks on campus:
Micr o$oft posters
Anomalous banners appeared upon Gates' visit
Everyone's heard of the CP car on the Great Dome. Don't ask how it got up there...you really don't want to know.
Hackers greet the new Institute president
Boston Pops VU meter during Esplanade concert
my personal favorite
We may be nerds, but dammit, we're FUNNY nerds. Browse around hacks.mit.edu for more.
To simply VIEW documents encoded in japanese, just take a file that's encoded with high-bit ascii and open it with netscape, and change the encoding to japanese. I'm not sure where you can pick these fonts up (they are in the standard distribution of Athena).
However, if you want to be able to EDIT japanese files, you'll need to use something like mule (multilanguage emacs), unless you're good with decoding high-bit ascii :)
To print these, look for jlpr, which takes a given input file and converts the high-bit ascii japanese characters to postscript. it's pretty nifty, but I'm not sure it exists outside of MIT's network (not sure if we wrote it).
Good luck,
Ken
Your flattery will never work against me, mere mortal! You shall never uncover the coveted secrets of PPC asm environments! mhuahahaha!
sleep deprivation kills
dammit, i want vi keys in these windows
Scientific studies have shown that the most limiting part of typing is being able to translate thought into physical action. The theoretical advantages to Dvorak have not been adequately proven.
I'm sure there is a theoretical maximum, but how that is reached varies. The brain creates what are called "engrams" for frequently used brain pathways. If I spent an entire day practing typing "hxb.,fihnxhb.fkns.huavhk.f,u.", I'm sure I could get VERY good at it, simply because the brain stops thinking "type h. Now type x. Now type b." and thinks, "run that engram for that weird thing." I've noticed that I can type certain key cominations VERY quickly (for example, "edit config.sys", a throwback to my DOS days).
So then the theoretical maximum keyrate becomes proportional to the rate of which nerve impulses travel from your brain to your hands. And we are probably probably NOWHERE NEAR that maxmimum
> FACT: With a QWERTY keyboard, only 30% of your keystrokes will be in the home row.
> FACT: With a Dvorak keyboard, over 70% of your keystrokes will be in the home row.
Again, this does not seem to be the major limiting factor to typing speeds.
It's not...but that's not the point...the point is that it's easier to type, which reduces the number or contorted hand keystrokes that you need to type any given work.
Another advantage with Dvorak is that there are very few words that you can type with one hand (papaya is one example), because the vowels and uncommon consonants are on the left hand, and commond consonants are on the right hand, so most words require switching back and forth between the hands, which is faster. Compare this to QWERTY, which has literally thousands of words that can be typed with one hand (devastate, etc.).
> You can realize for yourself what this means to the average typist.
Nevertheless, it has yet to be proven.
Proof is such a strong word...there can never be a PROOF that one is better than the other, since "better" is subjective. But there is very strong evidence and testimonials from those that have switched. I've never heard of anyone switching from QWERTY to Dvorak and back to QWERTY for any reason besides inconvenience of switching.
> These OSes have a program called xmodmap that makes it simple to switch their keys around.
This doesn't relabel the keys. It doesn't address the fact that no matter what OS you run, you will find yourself at someone else's keyboard.
That's true, but my school has a huge distributed system such that I can access my user account literally anywhere I can access an Athena machine. I work for Athena, my computer is a linux box running redhat/athena, so the only time i need to type in QWERTY is when I'm on someone else's PC running Windows, which is infrequent enough that it's not that much of a hassle. I'll jump back into QWERTY mode after a few minutes (just like riding a bike...). The human brain can be taught to switch back and forth between the two modes relatively easily...it just takes practice.
> As for hotkeys, deal with it. It took me about a week to get used to the new keys in vi--they don't have intuitive positions, but realistically, once you get used to them, it doesn't really matter ...
If it doesn't matter where the hot keys are, why does it matter where the other keys are? If the answer is to "get used to it", why bother? Why not "get used to" QWERTY?
if we're going to use that kind of logic, why not place the keys like "ABCDEFGHI..." Because it's really damn hard to type like that. Many programs use hotkeys with two conventions--either make them intuitively named (^C for copy, etc.), or they are placed conveniently (hjkl for vi et al). If it's the former, it doesn't matter where they are. If it's the latter, switching to any non-standard key layout will throw you off.
But it's more than just "getting used to" the position of the keys. I could "get used to" the purely alphabetical layout, but it would be too cumbersome to use (and very painful). Dvorak's key strength is ergonomics.
Dvorak is superior to QWERTY in almost all respects, and the ONLY drawbacks are due to the commonness of the QWERTY layout.
A very interesting article, but flawed. You can't judge the QWERTY/Dvorak debate solely on Economic grounds. Of COURSE it's a pain in the ass to relearn how to type. It can take up to a month before people are up to snuff in Dvorak (it depends on how much you have QWERTY ingrained--i.e., how much you look at the keys, how much you type words instead of letters (that is, you don't think "d-o-g-" when you type, you just think "dog"), etc.).
Dvorak spent over 10 YEARS developing the Dvorak layout, under the guise of a study for the Navy. He filmed typists, found the common problems, and fixed them. I'd like to see ONE study that supports the claim that QWERTY is as fast or faster. It just doesn't make sense:
FACT: Every national typing contest since 1931 has been won by a typist with a Dvorak keyboard.
One of the main reasons is that to execute extremely fast typing (I can do over 150 WPM in QWERTY, no joke), typists form "chords". For examle, to type "the dog" in QWERTY, a fast typist will place his or her fingers over all of the aforementioned keys and then just hit the keys in sequence. This is MUCH easier to do in Dvorak. Here is the Dvorak home row:
A O E U I D H T N S -
So to form a chord for "the dog", you only have to move off the home row for the G. You only move your hands off the home KEYS for the D and G, in fact. This is inherently better than QWERTY. Just watch your hands when you type either. QWERTY is ridiculous.
FACT: With a QWERTY keyboard, only 30% of your keystrokes will be in the home row.
FACT: With a Dvorak keyboard, over 70% of your keystrokes will be in the home row.
You can realize for yourself what this means to the average typist.
There are some disadvantages that others have pointed out. Leaving a keyboard in Dvorak will mess up friends who use your computer. Hotkeys are all messed up. Switching can be a pain in the ass.
But all of these are easily solvable. I run Linux, and I'd guess that a fair number of /. readers use some form of unixish OS. These OSes have a program called xmodmap that makes it simple to switch their keys around. So in my .login, I run "xmodmap $HOME/keyboard/linux.dvorak" (I also have files for Sun and SGI keyboards). This means that others can login to my computer with no problems. The keyboard itself is a QWERTY layout (I love the macro keys on Gateway 2000 keyboards). All the translation is done in software.
As for hotkeys, deal with it. It took me about a week to get used to the new keys in vi--they don't have intuitive positions, but realistically, once you get used to them, it doesn't really matter where the keys are. And if stuff like that really bothers you, hack the programs to change the hotkeys--it's pretty simple.
Switching back and forth will blow your mind the first few times you do it. As it is, I type Dvorak on every computer I log into, but if I am trying to fix something for someone, I will have to type QWERTY more than likely (I haven't managed to convince anyone to switch).
I liken switching from Dvorak to QWERTY to programming in several languages. It doesn't take me 10 seconds to forget everything I know about Perl and start coding in C, and the same goes for the other 10 languages I know--I never get confused, even though several of the languages have similar syntax (Java vs. C++, etc).
But I didn't intend this text to extoll the virtues of Dvorak and beat down the evil QWERTY. It's pretty obvious that Dvorak will stay where it is for some time until there is a sweeping revolution in the keyboard. We can't simply replace the keyboards in our schools with Dvorak because the teachers will refuse. Even if we did, the children who learned to type on these keyboards will only be able to type decently on these keyboards, and will be utterly confused elsewhere. I think the best compromise (at least until QWERTY/Dvorak hardware switchable keyboards are prevalent) is to have everyone learn QWERTY (because it's the most prevalent) *AND* Dvorak.
But enough ranting...
may you have better luck with the spell checker. it's spelled GRAMMAR.
sorry...that's just one of my pet peeves
So they were told it was going to be easy. Does that automagically mean that the school is REQUIRED BY LAW to make the class easy? That doesn't make sense.
Whose definiton of easy are we going to use? Ours? Then the university deserves to win. The average non-computer literate person's? Then the students should win.
You simply can't sue for misrepresetation unless there was some legally binding representation of the class.
I don't care how much they paid for the certification class. $1000 or more is nothing...I'm paying $25,000 per YEAR on TUITION here. Should I sue to get my money back because the classes are misrepresented as easy and I have trouble? The fact is that I have trouble in classes that are "easy" here. How is this so? Come to MIT if you want proof that you are not as intelligent as you once thought you were :).
Funny...I've never heard of anything like this before. This has to be the most absurd thing I've ever heard of in my entire life.
Maybe I'm jaded, but filing suit because a class was TOO HARD? About HOW TO USE MICROSOFT APPLICATIONS? I'm too disgusted to even laugh. I'd like to show these 12 morons my 6.002 (Electronic Circuits for non-MIT types) final exam from last term.
I wish I would have known that the prerequisites must encompass EVERY skill I need in a class. Hell, my discrete math class assumes I know how to add, but I didn't see that in the prereqs...they must be misleading me! Where's my lawyer?!
I can't even think of some twisted way to justify this suit. What I suspect is that these 12 slackers all took the class assuming it would be an easy one, and in true slacker form did not keep up with the work and hence failed. Very sad.
They failed the class. Obviously the class was either too difficult for them or they were too lazy. I can't begin to imagine how a class on M$ products would be too difficult for the average (hell, even far below average) college student to comprehend, so the only logical explanation is that they were lazy and it got them in the end.
I really hope they lose and the college files a countersuit. I have no respect for these people or for their lawyer. I'm not sure which is worse--laziness or greed.
The very fact that Gates mentions the fact that "Linux is not a threat" means that he already considers Linux a threat. The momentum has been building for the past few years.
I must admit that until very recently, I was running NT4/NT5/98. Not that I have anything against Linux, I just wanted to play games and game support for Linux, sadly, sucks. That should change soon when Q3A and a few other games are released commercially for Linux (maybe that will kick NVidia into realeasing drivers for their card and I won't have to reboot to play games at all). The reason I switched is that games became unimportant to me (relative to grades at least) and Linux has more functionality outside of games that Windows ever has (you wouldn't believe the amount of software available to me on MIT's distributed system, Athena).
Even though I only installed Linux a few months ago, I have been using UNIX since 1990 or so, and I toyed with Linux on my family's 486/33...I know countless Linux users that will never experience the joy of downloading the ~ 20 slackware disks on a 14.4 modem from sunsite, creating the dreaded root and boot disks (make sure they don't have a single bad sector before you RAWRITE them, or you'll ruin the disk!), etc. Linux is where it is today because there has been a push to make it more user-friendly...even in my day you had a color boot disk and the ability of UMSDOS, both of which made the transition from a DOS environment to Linux a bit easier)
So Linux has made definite progress in the five or so years that I've been using it. There is no reason to think that it will stop or even slow down. I doubt Gates loses sleep over Linux right now, but the fact that Linux is free and there are free alternatives to all of M$'s applications has got to at least make him sweat when these same applications get media coverage (for free, no less).
Bochs is similar in concept to this...an x86 emulator. One cool thing about Bochs is that it doesn't use any assembly code, so you can compile it on pretty much anything (I think i'll try it out on the UltraSparcs on campus some time). But that also means it's kind of slow (okay, a lot slow). Buuuut, "they" are working on dynamic translation, and premliminary tests show an increase in speed of several orders of magnitude (and that's just optimizing three instructions!). One other cool thing that i've noticed with bochs is that you can use your own VGA and BIOS ROM images...woowoo.
huh...that did it...just adding a device for ide0.1 that pointed to /dev/hdc did the trick! win98 loads and everything.
VMWare *almost* boots my windows partition...it /dev/hda, which has only windows installed), I get:
...
passes the bios screen and all that, but when LILO
tries to load (i use lilo on the MBR of
L 01 01 01 01
ad nauseum. I can't quite remember what that number means....does anyone know how to fix this, or at least get around it so i can boot from my DOS partition?