That's my video. I edited the OWSETENV.BAT file, but clearly forgot to
mention that in the video.

I actually did mention it in one of the takes for that video, but I had a
few false starts where I messed up near the beginning, and started a new
video. I guess I didn't mention the edit in the video that finally made it.

Yes, you need to edit for the correct paths.

Jim


On Thu, Sep 19, 2019 at 5:07 PM andrew fabbro <[email protected]> wrote:

> On Thu, Sep 19, 2019 at 12:34 AM Mateusz Viste <[email protected]> wrote:
>
>> Seems I have created the package with my custom paths. You will have to
>> fix that by hand - unfortunately FDINST/FDNPKG does not have any way to
>> modify any such configuration.
>>
>
> Easy enough.
>
>
>> I am not even sure OWSETENV.BAT is something that should be included at
>> all - might be a batch file I have created myself... If so, then the
>> reasonable thing would be to drop it from the package. And maybe add
>> some readme.txt that explains what should be set.
>>
>
> I learned about it from this YouTube video on the FreeDOS channel:
> https://www.youtube.com/watch?v=xuDEdCFr6eE
>
> Strangely, it worked fine in the example there, and that video was only a
> couple weeks ago, but possibly he's using some sort of updated (or
> non-updated) package.
>
> Should probably definitely be in a readme at least, as the various SETENVs
> are essential for sane usage.
>
_______________________________________________
Freedos-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to