Re: Re: Re: Re: Re: Re: Possible bug in latest VBox 5.2.8 triggered by E2B menu.lst

Tested latest E2B 1.98 with revised menu.lst (20180309) on VBox 5.2.8: NO BSOD for me.

Nice job Steve. It seems that 5.2.8 introduced some kind of wrong memory handling behaviour causing the problem with old line 504 instance. According to devs it's already fixed in currrent 5.2.9? dev build.

I'll keep testing 5.2.8 with latest E2B in the meantime.

Thanks a lot for your time looking into this and the continous improvement of E2B!
Starla 11/03/2018

New comment

To Top