Note that the article you link says that:
Newer Dataloader versions (45 and up) that use Zulu Java manage heap size differently and should not need to do this.
Are you certain that this is what you need to do? What are you doing that's bringing a memory error that you believe will be resolved by this?
That said, it's straightforward enough to pass ...
When you choose Browse, to select the Target for Extraction, and you choose a proper directory, does that help?
When I launched this on my mac, choosing "Browse" immediately suggested I save the file to my Downloads folder. Could folder access be the issue?
According to API Request Limits and Allocations - Concurrent API Request Limits:
Limits for various types of orgs for concurrent requests (calls) with
a duration of 20 seconds or longer:
Developer Edition and Trial orgs: 5
Production orgs and Sandboxes: 25
Unfortunately, I don't think you can do this in one load. ContentDocumentLink is what you need to insert that'll have a lookup to the file and the Knowledge Article. Both of those records need to exist to insert these records.
Dataload the files first. These are stored in the ContentDocument type.
After inserting, export the files to get the Id.
If you are trying to associate tasks with Accounts using the external Id.
The parentId field on task is polymorphic and can relate to different objects. The linking to Account won't work because of that.
Here is an Idea on IdeaExchange to have this implemented but it hasn't seen much traction as of now from Salesforce.
An easier way would be to query the ...
Rather than writing a series of OR clauses, use an IN clause to match many potential Ids.
Select ID, ParentId, RecordTypeId, OwnerId
WHERE Active_Client__c = TRUE
AND ParentId = null
AND RecordTypeId = '0111xxxxxxxxxxxxx'
AND AccountId IN ('0011111xxxxxxxxxx', '0011111xxxxxxxxxx', '0011111xxxxxxxxxx', ...)
You shouldn't ...