older versions of firefox for aspera connect

This is the log file of the program crashing and misbehaving in VirtualBox 5.2. Screenshot and VBox log file in attachment.ģ2bit OS are able to see up to 64GB of RAM with PAE activated, but are not able to allocate more than 2GB of RAM per process due to 32bit limitation, though. It's an install I've been working on flawlessly as programmer since 2001, which has been cloned several times to several different hard drives.

I also have no intention of migrating it into a virtual machine file. Hard Drive: Seagate SSHD 1TB Sata III (XP is installed on a Physical SSHD and I use it with the raw disk function. Anyway, limiting it to 4core didn't solve the issue). Guest: Windows XP Professional SP3 x86 + Microsoft Premium Support + PAEĬPU: 8 cores (I know VBox works with cores and not with thread, in fact I shouldn't assign threads to the virtual machine, 'cause timing would be terrible, but I do it anyway 'cause benchmarks shows that it slightly increase performances. Host: Fedora Workstation 26, updated constantly. Then I woke up, I went to work and I found out that my Virtual Machine had a blue screen caused by VBoxGuest.sys. I then left my computer open during the night to download files from a TV Studio using Aspera (these master files were fine and virus free, for the records).

Disabling it and doing a fresh install of it didn't solve the issue, though. I then tried to open Aspera Connect and it worked fine. I did some tests with Advanced Chromium (updated Chromium builds for XP) and Firefox 52 ERS and both were kinda slow. I turned the virtual machine off and on again, logged, same. The login was fine, but I noticed that some programs were misbehaving like Team Viewer and everything was kinda laggy (not smooth).

After updating from VirtualBox 5.1 to 5.2, I updated the Guest Additions in safe mode, rebooted and logged in my Virtual Machine (Windows XP SP3 Professional with the Microsoft Extended Support).

Older versions of firefox for aspera connect