Gammon Forum : MUSHclient : Suggestions : c++ support

Entire forum ➜ MUSHclient ➜ Suggestions ➜ c++ support

c++ support

It is now over 60 days since the last post. This thread is closed. Refresh page

Pages: 1 2 3 4 5 6

Posted by

Shadowfyr USA (1,791 posts) Bio

Date

Reply #75 on Wed 30 Jun 2004 09:26 PM (UTC)

Message

Quote:
i think Red Hats goin a lil too far with this enthusiast thing.

I mean cutting egde is cool, and bleeding edge is interesting, but carved up into tiny pieces edge isn't much fun.

It wasn't exactly Red Hat's fault. The 2.6 kernel has been in developement for some time and was assumed stable when finally released. The partition eating only happens on "some" older motherboards. The reason is due to a bug in the System bios that misreports information about the partition layout in an older format that XP still uses during bootup, but with has been replaced in every other OS by the use of the more reliable and modern method (LBA).

Basically:

1. Windows XP asks for partition info and gets: Sector 1 - yadda.. from the BIOS on drive C, then writes that into the partition table for the 'old' method.

2. You install Red Hat, which asks the hardware for info on the partition and writes that into the partition table, using the new method.

3. Windows XP boots, asks BIOS what the physical layout of the drive it is on is, looks in the drives partition table, finds information that is now incorrect and attempts to reload its bootloader from the physical location on the drive that 'used' to correctly refer to the logical location of that same data. Instead, the drive redirects it to the new 'logical' location pointed to by that info and Windows can't load.

This only happens on systems whose BIOS incorrectly report the 'true' physical layout of the drive, instead of the 'current' layout after being repartitioned. So, it is XP that is screwing up, not Linux. And it effects all Linux versons with the new kernel, since 2.6 tried to speed up loading by removing some files that would have normally checked for this BIOS problem and fixed it by writing what was actually incorrect info into the partition table for the old addressing method. Or at least that is what I understand about it anyway.

Top

Posted by

Seawolf USA (57 posts) Bio

Date

Reply #76 on Fri 02 Jul 2004 01:39 PM (UTC)

Message

Huh. That's pretty wierd.

Top

Posted by

Nick Gammon Australia (23,162 posts) Bio Forum Administrator

Date

Reply #77 on Sun 28 Nov 2004 12:55 AM (UTC)

Message

Quote:

LUA (www.lua.org) is an extension language that could do what you (finnish) want, if you can work out a way to implement it yourself.

Lua is now implemented in MUSHclient.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

Posted by

Nick Gammon Australia (23,162 posts) Bio Forum Administrator

Date

Reply #78 on Sun 28 Nov 2004 12:57 AM (UTC)

Message

Quote:

WINE and most others lack COM support. For most of us, COM and the scripting that depends on it is the #1 reason for using Mushclient.

MUSHclient's support of Lua in recent versions is not dependent upon COM, so that makes it a viable option to use MUSHclient on Linux (including scripting).

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Top

The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).

To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.

203,544 views.

This is page 6, subject is 6 pages long: 1 2 3 4 5 6

It is now over 60 days since the last post. This thread is closed. Refresh page

Go to topic: Search the forum

top