![eboostr settings.ini eboostr settings.ini](https://img.tamindir.com/resize/300x350/ti_e_ul/Lucifer/e-boostr-Capture2.jpg)
You can even try copying the track some more, to see how much more tracks you can play. You just download it, extract it, load it, and play it. If your Firewire connection is working at anything less than 400Mbit/sec, this should sound quite bad, as 100Mbit/sec gives you only 12.5MB/sec of firewire bandwidth. This should use a little bit over 24MB/sec of Firewire bandwidth. I created a project which uses 1 stereo 96kHz/32bitFP sine wave test signal at 220Hz across 32 tracks. That's even better, if you ask me, and the results will have much more significance for our needs ).
![eboostr settings.ini eboostr settings.ini](https://img.tamindir.com/resize/300x350/ti_e_ul/Lucifer/eboostr-build-cache-win7.jpg)
The easiest way to test the speed of a FireWire port would be external FireWire HD and some hard disk benchmark program like HDTach, but since you don't have any other FireWire devices, we will test it with audio. What do you think? RME guys say that the patch is kinda way to go.Įdit2: Actually, can you confirm that FW is not working properly in SP3? Everybody just assume that, but nobody confirmed.
#EBOOSTR SETTINGS.INI DRIVER#
This could be a very very cool "distro", me thinks :lol:Įdit: Right now, I'm not sure what to do: either to include the MS FW patch for SP2, or just simply to exchange the FW driver for the one from SP1.
#EBOOSTR SETTINGS.INI DRIVERS#
Would you be willing to test the FW performance if I make a new XP Installation CD with the older FW drivers included? I don't have anything FW audio here, just PCI and PCIe alltheway. There are some registry settings to tweak, too, AFAIK - It's not just a simple matter of replacing drivers. I could make them the default drivers, actually. I'm familiar with the issue and the RME page about it, no worries.
![eboostr settings.ini eboostr settings.ini](https://i1.rgstatic.net/publication/354710272_Science_in_the_Swiss_public_the_state_of_science_communication_and_public_engagement_with_science_in_Switzerland/links/61600f23ae47db4e57a5a707/largepreview.png)
So I guess this is the 3rd FR: include FW drivers from SP1 :). I'm also re-thinking of leaving Windows DEP on /executable=OptIn as DEP doesn't impair the performance and it can be useful to shield against "bad executable files".
#EBOOSTR SETTINGS.INI UPDATE#
I'm actually using this thread for FR's for the next update when nLite 1.4.2 comes out, lads and lassies, and so far got two FR's if I remember well: to leave those two default themes in, and to include SATA drivers.
![eboostr settings.ini eboostr settings.ini](https://docplayer.net/docs-images/84/89865942/images/26-1.jpg)
Contig is cool, but JKDefrag is much better and really fast defrag util.Īs for the FW drivers. SDelete is also cool as it cleans MFT, too. Have anybody noticed how fast the installation is compared to normal MS installation btw? and others: SysInternals utilities are great and very useful. However, if you have PCI express VGA card you don't need this at all.Īmberience, it would be nice to know if it works with Bootcamp as I haven't tried it myself, but I'm almost sure it works, because it's not that different from the "normal" installation, just a bit more optimised. The only thing you need to do with it is lower the VGA card latency to like 128 or maybe 64. Use doubledawg instead: I've been using it for years without any problems. :) So that's why I didn't get any notifications.Ībout PCI latency tool - I'd suggest you to use something else as it hosed my comp more than once with it's low level driver.