slow basilisk II

boomario · Post by **boomario** » Fri Aug 20, 2004 3:25 pm

i have basilisk II and basilisk II is very slow what's the problem
please help me!!

Stephen Coates · Post by **Stephen Coates** » Fri Aug 20, 2004 6:40 pm

errrrrmmm, errrrrrrrrrrrrrrrrrrrrrrrrrrrrr, errr, errrmmmmmmmmmm. how am I supposed to work that out? Could you post your BasiliskII config file and your system specs?

grayfox · Post by **grayfox** » Sat Aug 21, 2004 1:32 am

Are you trying to run this on a 486 by any chance

.

Mac Emu · Post by **Mac Emu** » Sat Aug 21, 2004 12:40 pm

BTW: Basilisk II is pretty quick on my P1 166 MHz laptop, but Fusion PC is much faster (plus I can play Aperion which Basilisk II can't do.)

On faster PC's, Basilisk II becomes faster then Fusion PC.

PPC_Digger · Post by **PPC_Digger** » Sat Aug 21, 2004 12:46 pm

Mac Emu wrote:On faster PC's, Basilisk II becomes faster then Fusion PC.

More like on faster PC's that run Win 2000/XP.

Also, since the pentium-pro intel has dropped the real-mode code so they have to emulate - so basilisk works better because it's 32-bit compared to fusion which is 16-bit (emulation vs. emulation-in-emulation).

Mac Emu · Post by **Mac Emu** » Sat Aug 21, 2004 1:42 pm

Fusion PC isn't 16-bit. It's 32-bit optimized assembly code that requires a 486 or higher.

PS: My P1 166 MHz laptop is running Windows 2000 (and Windows 98se).

PPC_Digger · Post by **PPC_Digger** » Sat Aug 21, 2004 2:24 pm

Mac Emu wrote:Fusion PC isn't 16-bit. It's 32-bit optimized assembly code that requires a 486 or higher.

PS: My P1 166 MHz laptop is running Windows 2000 (and Windows 98se).

Are you sure? (about fusion) - it's protected mode?

PS: My dad's P1 MMX 150 MHz laptop is also running windows 2000 and 98 se.

Mac Emu · Post by **Mac Emu** » Sat Aug 21, 2004 3:54 pm

Yes. About 5 years ago on the Fusion PC mailing list, Jim Drew discussed a little about the assembly code used in Fusion PC.

It uses a 32-bit DOS extender in order to run in protected mode under DOS. Thus it uses the extended registers like EAX, etc. in a FLAT memory model instead of the 16-bit registers like AX, etc. in a segmented model (which DOS uses). Fusion PC is also code optimized (by hand) for 486 and higher processors, so it will not run on anything earlier (whereas I imagine Basilisk II could run on a 386DX running Windows NT\9x).

grayfox · Post by **grayfox** » Tue Sep 14, 2004 10:44 pm

PPC_Digger wrote:
Mac Emu wrote:Fusion PC isn't 16-bit. It's 32-bit optimized assembly code that requires a 486 or higher.

PS: My P1 166 MHz laptop is running Windows 2000 (and Windows 98se).
Are you sure? (about fusion) - it's protected mode?

PS: My dad's P1 MMX 150 MHz laptop is also running windows 2000 and 98 se.

dam u got 2000 running on a 150mhz CPU that must be slow

PPC_Digger · Post by **PPC_Digger** » Wed Sep 15, 2004 6:39 am

grayfox wrote:
PPC_Digger wrote:
Mac Emu wrote:Fusion PC isn't 16-bit. It's 32-bit optimized assembly code that requires a 486 or higher.

PS: My P1 166 MHz laptop is running Windows 2000 (and Windows 98se).
Are you sure? (about fusion) - it's protected mode?

PS: My dad's P1 MMX 150 MHz laptop is also running windows 2000 and 98 se.
dam u got 2000 running on a 150mhz CPU that must be slow

It is slow, but not because a slow CPU, but because the lack of memory (2000 is really slow with 80mb, paging all the time).