First issue is that I cannot locate the ZIP file download of the x64 version of Burn-In-Test 5. I found the x86 version in the FAQ, but not the x64 copy.
Second issue is much more frustrating. Every time I run BIT on a machine, it insists on looking for the lastused.bitcfg in "My Documents\PassMark\BurnInTest", even though I have my custom configured lastused.bitcfg already made up in the existing directory. This is very frustrating, to say the least. BIT 4 did NOT have such an issue. It would always look in the current directory first, and only if it did not find one would it complain (or would make it's own default, I can't remember now).
In my opinion, this is a severe regression that needs to be looked at and fixed. I shouldn't have to jump through hoops to make it use my already existing config file. Sure, I can copy the lastused.bitcfg to that directory first, or I can create a batch file that forces BIT 5 to look in the current directory with the /p command, but that's just a waste of time for a "feature" that shouldn't exist.
I'd appreciate any comments or suggestions, if maybe there's some option in BIT that I'm overlooking to make this work already, but I've looked pretty throughouly and am pretty sure that it's not there. Thanks.
Second issue is much more frustrating. Every time I run BIT on a machine, it insists on looking for the lastused.bitcfg in "My Documents\PassMark\BurnInTest", even though I have my custom configured lastused.bitcfg already made up in the existing directory. This is very frustrating, to say the least. BIT 4 did NOT have such an issue. It would always look in the current directory first, and only if it did not find one would it complain (or would make it's own default, I can't remember now).
In my opinion, this is a severe regression that needs to be looked at and fixed. I shouldn't have to jump through hoops to make it use my already existing config file. Sure, I can copy the lastused.bitcfg to that directory first, or I can create a batch file that forces BIT 5 to look in the current directory with the /p command, but that's just a waste of time for a "feature" that shouldn't exist.
I'd appreciate any comments or suggestions, if maybe there's some option in BIT that I'm overlooking to make this work already, but I've looked pretty throughouly and am pretty sure that it's not there. Thanks.
Comment