Anyone?! 😢

I installed them sucessfully on my systems some time ago (before the VOGONS thread you mentioned was created). Can't remember where I got the files though.

It would help if you posted the error message that came up before the installation went wrong.

5u3 wrote:

I installed them sucessfully on my systems some time ago (before the VOGONS thread you mentioned was created). Can't remember where I got the files though.

It would help if you posted the error message that came up before the installation went wrong.

This is what it looks like:

Here you see that the paths are correct acoording to the instructions in the pro patch (PPL150) folder

This is the error I get when try to launch the patch process with the corecct command:

The patch menu without directly launcing the patching by command line:

The result after choosing "S" which is the same as lancing the patch process with the command line:

1#define DOSERR_ACCESS_DENIED 5

This is errorcode 5 access denied. Did you check with attrib for read only ?

Qbix wrote:

This is errorcode 5 access denied. Did you check with attrib for read only ? […]
Show full quote

Copy code to clipboard

1#define DOSERR_ACCESS_DENIED 5

This is errorcode 5 access denied. Did you check with attrib for read only ?

How do I check that?

Maybe my ULTRASND folder is read only...... 😵

attrib

Qbix wrote:

attrib

Seems like it only checks files and not directorys but now I've set all files in the ultrasnd + other subdirs to "archive" attribute but still get the same error 😕

Edit: now I have set all folders so they have an "A" as attribut but still same problem

A(rchive) means that the next time you backup program is run, this file should be be archived.

MiniMax wrote:

A(rchive) means that the next time you backup program is run, this file should be be archived.

doh! mys dos skills is a bit err....rusty 😁

So what syntax shall I use with the attrib command?

http://www.computerhope.com/attribhl.htm

I used ex. "attrib -r C:\ULTRASND"

-R means clear/minus the Read-Only bit.
+R means set/add the Read-Only bit.

MiniMax wrote:

-R means clear/minus the Read-Only bit.
+R means set/add the Read-Only bit.

mmm....so what exactly what command make my dirs "writable"?

Doesn't seem to exist such a command syntax 😕

What attributes (read-only, read/write, archive, hidden, non-hidden, system, non-system, blue, yellow, green or murky) are set on that damned directory?

http://www.microsoft.com/technet/archive/msdo … 1.mspx?mfr=true

MiniMax wrote:

What attributes (read-only, read/write, archive, hidden, non-hidden, system, non-system, blue, yellow, green or murky) are set on that damned directory?

http://www.microsoft.com/technet/archive/msdo … 1.mspx?mfr=true

A damned "A" 😁 when I check the attribute with "attrib" and with DOS NAVIGATOR file manager

Well then fire up some debugger and see why int21/3d or similar fail.
As Qbix already noted the runtime error signals failed access to some
file be it in the original directory or in some directory it wants to update,
maybe even config.sys or whatever.

wd wrote:

Well then fire up some debugger and see why int21/3d or similar fail. As Qbix already noted the runtime error signals failed acc […]
Show full quote

Well then fire up some debugger and see why int21/3d or similar fail.
As Qbix already noted the runtime error signals failed access to some
file be it in the original directory or in some directory it wants to update,
maybe even config.sys or whatever.

I really suck when it comes to DOS, when you say debugger...is there a utility like SNOOPDOS like we have on the Amiga?

Amigaz wrote:

wd wrote:

Well then fire up some debugger and see why int21/3d or similar fail. As Qbix already noted the runtime error signals failed acc […]
Show full quote

Well then fire up some debugger and see why int21/3d or similar fail.
As Qbix already noted the runtime error signals failed access to some
file be it in the original directory or in some directory it wants to update,
maybe even config.sys or whatever.

I really suck when it comes to DOS, when you say debugger...is there a utility like SNOOPDOS like we have on the Amiga?

Update:

Found a snoopdos variant for PC DOS but not sure vhat to tell from this below, it just seem to stop after attempting to apply to first patch?

Top of report:

End of report:

errmm...got it working 😁

You guys were right all along...it was a "read only" attrib issue 😉

Which file(s) were that?

wd wrote:

Which file(s) were that?

All the .pat files were READ ONLY 😜

Damn...WinRAR on my Mac had removed the correct attributes when I unpacked them

Had to change the attribs on the 1.60 + 1.61 versions of the propatches now also

Thanks everyone who pointed me in the right direction 😀