> > [Hrm - looking closer at that HTML link I sent before, it says > > specifically "Per-machine installs must install to Program Files > > by default in order to > > pass this test case" - that seems pretty clear...] > > Given that the links in Gerald's examples were under Program Files, I > had assumed that HP were tweaking the installer at least that much... But wouldn't that leave us in the situation where Python's installer is *not* "OEM Ready", nor has it been certified as such - but an installer based on ours, but with unspecified changes has? Of course, I don't object to that and still think we should help where we can, but if that is true it would make the premise of this thread a little misleading, as obviously HP could then make *any* necessary changes without our agreement or even knowledge. Cheers, Mark
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4