Keep up the good work!

I love the spirit of your programs: Do one thing and do it well.

I much prefer having a host of small programs to choose from than one big, bulky Swiss Army Knife-style program. Worse yet, kludge more into the OS and watch it bloat out of control!

Thanks,

TJH

One quick suggestion for JoinSplitter would be the option to show the filesize in megs instead of just k's. That would be handy for some of the large files we have these days.

_________________
'unfixed' A1XE, 512mb RAM, plug-in USB card, Sil 0680 IDE card, Radeon 9250, built-in sound, OS4.1 update 5.

Go Deniil go !

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

Great updates Deniil.
You're one of the greatest, keep up with the great work
you're doing for the Amiga world.

_________________
---------
AmigaClyde

µA1-C 750GX@800 using OS4.1

Thanks for your continuos support Deniil715!

Although this problem might be misplaced on this site...But TheMPegEncGUI still doesn't work together with MUI4 on MOS. Have you investigated into this problem?

Last edited by _analogkid_ on 01-Dec-2007 at 07:50 AM.

As Racer says showing in megabytes would be nice.
I love onyxsoft releases. Always some good stuff updating.

Thank you for the BackUp update, guys.. I use it every week on my A1.

@All

Thankyou very much for your kind words! I have another batch in the queue to be released soon after I have ironed out a few bugs and fixed my small electronic project

@RazorX
I have added the megabyte thing to my todo-list for JoinSplitter. Let's see what happens.

@_analogkid_
About The..GUI and MUI4. I haven't dug any deeper in this. The strange thing is that The..GUI uses the same input-loop as all my other MUI program which seems to work fine. I don't know what's causing this behaviour with MUI4 on MOS.

It seems that when a gadget is clicked, it is not reset but it keeps trigger the click forever. I don't have a Peg to test on and Develin (Stefan) doesn't appear to be very productive anymore since he got a child and all. I'll see if we can get it sorted out sometime.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

version 2.5 (2004-12-14) works without any problems with MOS and MUI4 while the latest not (no hits ... only the message

excessive gadgetclicking, quitting now.
Do you by any chance run MOS with MUI4..?

Edit- the 2.64 lite crashes the whole system while the 2.64 full, not

Confirmed that 2.5 (2004-12-14) works as aspected.

Last edited by Framiga on 01-Dec-2007 at 04:28 PM.

_________________

Quote:

BackUp v1.50 - (68k) Backup program that mirrors a directory structure. Added more parameters to use BackUp from CLI. BackUp can now follow links, or ignore links completely.

i use bakitallup from cj wenzel which works nice. it does not look so nice imho. could the backup tool be enhanced to allow several "backups" at once - just like backitallup does it? currently only one dir can be mirrored.

thanks and
byebye...

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

To do several backups, you can create a script like mine:

Quote:

ECHO backing up dh0: ... BackUp SOURCE=dh0: TARGET=BACKUP_dh0: BACKUP AUTOQUIT ; ECHO cleaning backup_dh0: ... BackUp SOURCE=dh0: TARGET=BACKUP_dh0: CLEAN AUTOQUIT ; ECHO backing up dh1: ... BackUp SOURCE=dh1: TARGET=BACKUP_dh1: BACKUP AUTOQUIT ; ECHO cleaning backup_dh1: ... BackUp SOURCE=dh1: TARGET=BACKUP_dh1: CLEAN AUTOQUIT

Nice!

For Backup, I would like to see one more option regarding links support: If a link points to somewhere inside the tree that is being copied, recreate it (as link) in the destination tree (yes, I know, it will require some extra thinking to make sure it isn't attempted to be created until the link's target has been copied, but it should be possible). If the link points to somewhere outside the tree, just clone the link in the destination, pointing to the same target as the original link does.

This feature would e.g. make it possible to make a backup of the SDK which needs no post-cleanup.

Edit: Oh, and why no native OS4 version?


Best regards,

Niels

Last edited by nbache on 01-Dec-2007 at 11:27 PM.

@Deniil715:

If you need some assistance regarding tests together with MUI4, I could help, if you want. I would be very glad if it works again together with MOS

mhhh! it looks like he is not interested to fix it :-/ (and btw, not that easy when you come to face MUI4 ... a MUI4 SDK reading is required at least)

_________________

sure - with scripts it may work.
but i want a nice gui to do it and to see the progress in general.

byebye...

_________________
Michael Merkel
(Michael.Merkel@gmx.net Home)
Member of Amiga-Freunde Pfalz, OS4 Welt

Quote:

About The..GUI and MUI4. I haven't dug any deeper in this. The strange thing is that The..GUI uses the same input-loop as all my other MUI program which seems to work fine. I don't know what's causing this behaviour with MUI4 on MOS.

I wonder how you are detecting gadget clicks... counting them in the input loop is not very good idea because it can run even when gadgets are not clicked.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@nbache

Quote:

Edit: Oh, and why no native OS4 version?

He writes his code in the AmigaE programming language which hasn't been ported to AOS 4 yet.

@MichaelMerkel

As jahc says, scripts is the only way now. The thing is also that I like to keep it simple to prevent inducing bugs due to lack of complex texting.

@nbache

Since it is recursive and all it seems difficult to keep track of links to be able to determine if they are recreatable or not. For now it will copy the file it points to. I will try to change this though so that it copies the link itself instead. This will work fine with relative, or assign links, but not with absolute links (unless you move you backup back to the source before you use it).

Quote:

Edit: Oh, and why no native OS4 version?

Becuase it is written i Amige-E, and I like it to work on all systems. (Sorry AROS.)

@itix & all

About The..GUI and MUI4. I don't know where to start searching for this problem. I count gadget clicks to detect the problem, yes. If the user hits the same gadget 10000 times in a row without touching anything else in between, this message shows up. on MUI4 the fist gadget clicked seems to stick in click mode and therefore generates 10000 clicks in a blink. Only the full version has this protection code, the other versions hang.

The input loop looks roughly like this:

muisig:=0
REPEAT
  thez:=doMethodA(maingh,[MUIM_Application_NewInput,{muisig}])
  IF thez=MUIV_Application_ReturnID_Quit ; quit:=TRUE
  ELSEIF thez<ID3_ID ; proc_normal(thez)
  ELSEIF thez<MPEGA_ID ; proc_id3(thez)
  ELSEIF thez<LAME_ID ; proc_mpega(thez)
  ELSE ; proc_lame(thez)
  ENDIF
  IF muisig
    muisig:=Wait(muisig OR Shl(1,sigbit_sub) OR timer.sig)
    IF muisig AND Shl(1,sigbit_sub)
      muisig:=muisig AND Not(Shl(1,sigbit_sub))
      handle sub process......
    ENDIF
    IF muisig AND timer.sig
      muisig:=muisig AND Not(timer.sig)
      take care of timer......
    ENDIF
  ENDIF
UNTIL quit

This is how I do it in all my MUI programs. On MUI4 MUIM_Application_NewInput apparently keeps returning the last ID over and over. Perhaps it needs to be reset somehow?

Last edited by Deniil715 on 02-Dec-2007 at 06:36 PM.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

Quote:

@nbache Since it is recursive and all it seems difficult to keep track of links to be able to determine if they are recreatable or not. For now it will copy the file it points to. I will try to change this though so that it copies the link itself instead. This will work fine with relative, or assign links, but not with absolute links (unless you move you backup back to the source before you use it).

Yes, as I said, it is not straightforward, but it's not that hopeless either. What I would do is make some sort of global collection (tree, map, list, array or whatever you prefer; I guess a linear one -- list or array -- would suffice) and collect all encountered links in it when you are about to copy them. Then just copy them as you do now (or maybe just save a dummy file to reserve the name in the dir). After you come back up from the whole recursion, walk that collection and change each of the links to what they are really supposed to be. At that time all targets within the copied tree will be created and can be linked to, and those outside of it will have been there all the time. But you don't have to distinguish between the two cases if it is impractical during the recursion. Of course, if you *can* distinguish, you could save some work by creating the "outside" links on the fly and only save the "inside" ones for the postprocessing.

Note: I haven't tested this algorithm, it's directly from the messy inside of my head.

Quote:

Quote: Edit: Oh, and why no native OS4 version? Becuase it is written i Amige-E, and I like it to work on all systems. (Sorry AROS.)

Ah. Right, I remember now. My condolences.

(just kidding, of course. Chacun a son goût.)

Best regards,

Niels

@nbache

I'll thing about this, or some other way of preserving the links.

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.