LB Booster
General >> General Board >> LBB on MAC OS X using Crossover
http://lbb.conforums.com/index.cgi?board=general&action=display&num=1447603352

LBB on MAC OS X using Crossover
Post by BrianM on Nov 15th, 2015, 3:02pm

Just for information - LBB 3.30 does work on Mac OS X El Capitan 10.11.1 using Crossover 14.1.11. Crossover is a commercially supported version of Wine.

The only problem is that setting temporary breakpoints in the editor is hit and miss (most of the time they are either not set or the markers are not set, I cannot tell which) and if markers are set the do not scroll with the editor text. This is probably a Wine issue so I do not expect a fix.

Compared to LB
L4B4.5 does not run - unable to allocate virtual memory.
LB4.04 runs but using the toolbar in the editor creates a stack overflow error. Using the menu is OK. This was not seen with Crossover version 13.

So far no problems seen with BB4W.

Brian

Re: LBB on MAC OS X using Crossover
Post by tsh73 on Nov 15th, 2015, 3:41pm

Brian,
Quote:
L4B4.5 does not run - unable to allocate virtual memory.

if you are LB forum member, I really think you should post it there.
For the common good.
(not that "FOR THE GREATER GOOD" if you have read Harry Potter series)
Re: LBB on MAC OS X using Crossover
Post by Richard Russell on Nov 15th, 2015, 3:45pm

on Nov 15th, 2015, 3:02pm, BrianM wrote:
Just for information - LBB 3.30 does work on Mac OS X El Capitan 10.11.1 using Crossover 14.1.11.

I am aware of several incompatibilities with Wine, which may well affect Crossover too:
  1. LBB does not even run unless you manually create the %temp%\lib directory first. This is a symptom of Wine Bug #25207.

  2. You cannot create an executable on a drive different from where LBB itself is installed. This appears to be due to an incompatibility in the Wine implementation of the MoveFileEx API.

  3. The Change icon button does not work in the Make Executable dialogue. This is because Wine does not implement the PickIconDialog API (exported as ordinal 62 from SHELL32.DLL).

  4. You cannot paste into the editor. This is a symptom of Wine Bug #14530.
Quote:
The only problem is that setting temporary breakpoints in the editor is hit and miss

I have not had that reported before. I don't know what the cause might be.

Quote:
L4B4.5 does not run - unable to allocate virtual memory.

This is a known issue that can affect Windows too. It happens because LB 4.5.0 attempts to allocate 1 Gbyte of contiguous virtual memory (address space), and there is no guarantee that it will be available. Carl is aware of this problem (although I'm not sure he understands it properly) and the simplest fix is to allocate less memory (LBB allocates 512 Mbytes, by default, although it is configurable in the lbb.ini file).

Note that in Windows there is a difference between reserving virtual memory (which allocates address space only) and committing virtual memory (which makes sure that the requested memory can be made available, if necessary from the swap file). In Linux there is no such distinction, so in Wine the two operations have exactly the same effect. This may (or may not) make the problem more likely to occur.

Richard.

Re: LBB on MAC OS X using Crossover
Post by Mystic on Nov 18th, 2015, 6:14pm

Nobody said it this way on here, but Richard! Have you considered attempting to convert LBB over to MAC?

Is it even a possibility (I know it's very Windows-centric).

Sorry, most of my world revolves around MAC and I would love to see a LBB like version of BASIC on that platform. smiley
Re: LBB on MAC OS X using Crossover
Post by Richard Russell on Nov 19th, 2015, 01:35am

on Nov 18th, 2015, 6:14pm, Mystic wrote:
Have you considered attempting to convert LBB over to MAC?

No.

Richard.

Re: LBB on MAC OS X using Crossover
Post by tsh73 on Nov 19th, 2015, 06:10am

Code:
Have you considered attempting to convert LBB over to MAC?  

There are some reasons stated in this thread
Winding down LBB
see reply #17 and #28
Re: LBB on MAC OS X using Crossover
Post by Mystic on Nov 21st, 2015, 6:17pm

on Nov 19th, 2015, 06:10am, tsh73 wrote:
Code:
There are some reasons stated in this thread 


Thanks for the reference. Still saddens me... :(