Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
55 user(s) are online (27 user(s) are browsing Forums)

Members: 0
Guests: 55

more...

Headlines

Forum Index


Board index » All Posts (jPV)




Re: About off topic news on Amigans
Just popping in
Just popping in


@geennaamQuote:
geennaam wrote:

Things with Morphos seems to have calmed down as far as I can tell.

Ironically, the attacks on amigaworld towards os4 now come mainly from the vintage 68k crowd.

Yeah, I think that mentality has changed so that Amiga compatible PPC operating systems (OS4 and MorphOS) have to defend their place against 68k fanatics, and partly against AROS crowd too. After all, OS4 and MorphOS are the closest relatives by features, philosophy, and goals, so they're pretty much in the same boat nowadays . And it's nice to see that there's more cooperation than fighting between these camps nowadays.


Quote:
But the sites statement of intent includes 68k emulation and vintage 68k systems as well. Without further specifying if this is with or with our direct link to os4.

That's always been a bit confusing for me, because when it doesn't require a direct link to OS4, then it basically opens the door for a wider selection of platforms. But as I know the history of the site, I still wouldn't post news items about someone running AmigaOS3.9 over the MorphOS kernel, or such :) I think it's fine that there's a site purely for OS4, but it shouldn't boast also being for emulation/classic without further declaration.

Go to top


Re: How much this 2d cartoon animation video is close to 8bit Pixel Art ?
Just popping in
Just popping in


I think it would be much better without the over the top dithering. If the 8bit refers to colors (256), then there is no need for that harsh dithering in this kind of solidly colored material. I think it would still work fine with even less colors when picked correctly without trying to fake shades with dithering for the sake of trying to add some kind of "authenticity".

Go to top


Re: Bug RNOXfer
Just popping in
Just popping in


Good to hear, thanks for reporting!

Go to top


Re: Bug RNOXfer
Just popping in
Just popping in


Maybe this works better, or at least more consistent now. I think there was some bug in Hollywood and plugin locations that could affect to this, which has been fixed.

I have also changed charset handling for the new version now. Earlier versions didn't support UTF-8 in filenames, but handled non-English characters in ISO/Amiga charsets, which basically is against FTP specifications, but old Amiga FTP clients did that too and some servers didn't care. I've now made the program to work according the specs and non-English characters are allowed only in UTF-8 if a server supports it.

Here's a change log for the new version I just released:

Version 1.4:
- Added editing fields in the server list window
- Added the comment column on the server list
- Added the default local path setting
- Added the private keyfile setting for SFTP connections
- Added a check for server list changes at exit
- Added UTF-8 support to be RFC 2640 compliant
- Massive speedup in directory handling
- More verbose file size comparison when a file exists
- Added an option to save selected files/dirs as a text file
- Fixed advanced.conf handling
- Fixed issues with the settings file format
- Adjusted window sleep modes
- Disconnects from the previous server when double-clicking a new server from the server list
- Uses hURL 2.0 (requires AmiSSL 5 on AmigaOS)

Go to top


Re: MorphOS 3.18 is out
Just popping in
Just popping in


Hmm.. as the thread is here, here's something I've created recently about the new MorphOS 3.18 release:

A video about the really nice integration of Samba (Smb2FS) in Ambient, this is how it should be made:
YouTube video

And info/screenshots of the new programs:
Hex, ArchiveIt, Thermals, and Smb2FS

Go to top


Re: Dynamite- bomberman clone
Just popping in
Just popping in


@VooDooQuote:
VooDoo wrote:I do not know how many of you played this game but I know that I spent a lot of hours, nights on it :)

I did play it a LOT.. many nights/weeks/months lost back in the day :) It was when there wasn't a public release, but in beta stage... I think the public version got a bit too bloated and started to have more lag etc and I lost the best interest then.

Quote:
Maybe is time to arrange an date to play some death matches :) what you say?

I guess it would be fun to try after a very long time, and setting a date/time would be the best shot nowadays.

Go to top


Re: HTML editor with Syntax Highlightning
Just popping in
Just popping in


Cubic IDE is pretty sweet for HTML too.

Go to top


Re: Dump drawer contents to text file with date file size and version number?
Just popping in
Just popping in


I've been using Magellan2 since 1998, so I don't remember if DOpus4 had configurable columns (or even per dir ones). And if the original doesn't, I also don't know if this feature has been added to newer open source ones... sorry.

Go to top


Re: Dump drawer contents to text file with date file size and version number?
Just popping in
Just popping in


I just have the Version column enabled for Libs:, C:, and such directories in DOpus... and then you can print the directory to a file with it too :)

Go to top


Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


@tekmageQuote:
tekmage wrote:@jPV

The fun part about this situation is it only happens on X5000s. Other OS4 platforms don't have this crash!

I bet the actual bug happens on all setups, but it might be just pure luck if it becomes a visible/fatal issue. For example, if it trashes memory, it trashes it every time, but how it shows up depends on what contents it trashed. Maybe X5000 just happens to have some crucial data (drivers or so) on the affected area more likely than some other setup.

The bug I reported is reproducible on both WinUAE and X5000, but at least on WinUAE it's random and you'll have to try to trigger it a bit more before it actually crashes.

Go to top


Re: Pixy new pixel editor for amigaos4
Just popping in
Just popping in


Quote:
tekmage wrote:@Raziel

I am not 100% sure but having looked at this a bit I think the Hollywood directory under storage is dynamically created during the runtime of the Hollywood App. Here are my current sys:storage dir:

Hollywood used to create these temp files if a 3rd party application was compiled to link plugins in the executable (this is why I didn't link plugins in my programs but included them in the progdir). Hollywood cleared these temp files when you quitted the program, but files were left there if you rebooted or crashed without quitting the program.

This has improved in Hollywood 9.0 and you can avoid temp files creation even when linking plugins. This is the changelog entry:
Quote:
- New [OS3/OS4/MorphOS]: Linked plugins will now be loaded directly from the executable or applet without
using temporary files; note that this only works for uncompressed executables or applets; if you activate
compression, temporary files will be created



Quote:
eliyahu wrote:@sinisrus

Just picked up the latest alpha on OS4Depot and still getting same crash on my X5000 that many have also experienced

This looks a bit like the issue I have with mui.CreateObject with Hollywood on OS4, I don't know if the same function is used in Pixy. Anyway if you do dynamic runtime object creation on OS4, it seems to be a problem. This doesn't happen on any other platforms, but only on OS4.. so probably codesets.library or OS4's MUI implementation issue. Here's more information about my findings: link

Go to top


Re: Morphos 3.15 stopped booting on my AmigaOne X5000
Just popping in
Just popping in


@SkatemanQuote:
Skateman wrote:
Since AmigaOS and MorphOS by default both use a DH0, DH1 SYS: WORK: etc.. i did this... (if i recall correct)

I installed morphos on a seperate HD using the folowing..

DH0 => became DH0.1 and i labeled this MOSSYS:
DH1 => became DH1.1 and i labeled this MOSWORK:

You probably remember wrong, because labeling to MOSSYS: will break things. MorphOS has the MOSSYS: assign which points to the SYS:MorphOS/ directory (MorphOS separates OS files from user files, and OS files reside in this assign). So, relabeling a drive would collide with it.

To avoid confusion I would change the device names of partitions manually to something more explanatory rather than letting OS name them as .1 etc. It's best to do this before or immediatelly after installing the OS, before any applications or configs start pointing with device names (which is a bad practise anyway, but some will do it anyway).


SYS: is always automatically assigned to the partition that system was booted from, so this works correctly always and no need to worry about it, and never try to change it in any case.

I probably would rename device names of MorphOS partitions, for example, to MDH0:, MDH1:, MDH2: etc.

By default the volume name for the system partition is Workbench: on AmigaOS and System: on MorphOS, so this doesn't clash and you can leave them on those names.

Other partitions like Work: can be relabeled as you wish. For example, MOSWork: would work :)

Go to top


Re: LHA Archiving questions....
Just popping in
Just popping in


Well.. I combined this with another script I've made earlier, and here's the result: download

Features:
- Creates separate archives of directories from the source dir
- Adds directory icons into the archives if found
- Handles spaces in dir names
- Progress output on the shell
- If there were errors while archiving, it informs on which dirs it happened
- Can be used with DOpus ("Execute S:archive_dirs.script {s} {d}", output to window)

Usage:
- Execute archive_dirs.script SOURCE DEST
- Important: DEST must end to : or /

Resized Image

Hope it doesn't contain much bugs :)


Edited by jPV on 2022/4/12 18:06:39
Go to top


Re: LHA Archiving questions....
Just popping in
Just popping in


@CagemanQuote:
Cageman wrote:@jPV

Ahh... yes... well... I got a similar but different solution... see my previous post... I must have made that post while you were making yours. :)

Heh, yeah, but you got an ugly solution ;) Why to use 3rd party tools when you can do it in OS, and I also think that the solution you got doesn't work when there are spaces in directory names.

Go to top


Re: LHA Archiving questions....
Just popping in
Just popping in


@Cageman

This can be done in the Shell quite easily, for example, like this:
List DIRS LFORMAT="LhA -a -e -x a *"%N.lha*" *"%N*"" T:lha_script
Execute T
:lha_script


This works if you CD into the corresponding dir first, and it creates archives in the same dir. But you could expand this to a better script which would take source and destination directories as arguments.


Edited by jPV on 2022/4/11 17:30:01
Go to top


Re: Bug RNOXfer
Just popping in
Just popping in


Hmm.. I don't remember I've changed anything related in the code, on purpose at least, but I'll try to check it... thanks for the report anyway.

Go to top


Re: AmigaOS 3.2 for all Classic Amigas released and available
Just popping in
Just popping in


@TSK

Quote:
I forgot the buffer size setting completely. I formatted the other CF card with the default block size 1024. So which way I should do, smaller block size or even bigger ?

Amiga filesystems (like SFS) have traditionally recommended to use block size of 512, which is basically good for small files and it wastes less space from the disk. But if you want to speed up handling of big files (like media files, archives, etc), then you might want to consider using bigger values... 1024 as a moderate compromise, 2048 for focusing more on the speed, or even 4096.

The bigger the value is, the more it consumes memory (buffers * blocksize bytes for each partition, 500 buffers with 1024 bs would consume 500kB of memory) and more you waste disk space (if you have a 20 bytes config file, it will take 4096 bytes from hd with 4096 bytes block size). So, I wouldn't recommend big block sizes for a boot partition, which contains thousands of small files.

In my opinion buffers have actually bigger impact on speed with many real world operations (like when deleting/scanning files) than the blocksize. So if you don't have that much memory, I would use small blocksize, but at least moderate amount of buffers. IIRC HDToolbox on 3.x had default value of 60 or 80, or something like that under 100, for buffers. IIRC SFS documentation recommended to use 128 buffers or so, and I've felt that it's quite good to have it over 100 or couple hundreds on classics. On NG I personally have raised buffers to 4096 on partitions I have lots of small files and I need to delete large amounts of files regularly, and 2048 on other partitions. It really shows in speed when you delete, for example, a system backup directory.

As said, buffers can be changed easily, but changing the block size will need a re-format of the partition. So it'd be more important to decide the block size before taking a new disk in use.

Go to top


Re: AmigaOS 3.2 for all Classic Amigas released and available
Just popping in
Just popping in


@Steady

Hmmm... why would disk space affect to memory consumption? Isn't it mostly Buffers * Blocksize in this case? On NG machines people might use buffers as hundreds or even thousands, because memory isn't an issue there, but on classics I'd stay somewhere like 128 or so. And keep blocksize as 512 if there isn't a good reason and memory to make it bigger.

Buffers can be set in HDToolbox or checked (or modified temporarily) by the AddBuffers command.

Go to top


Re: Looping in DOS batch scripts
Just popping in
Just popping in


I once made a file size based counter ;) I don't know if there would be other way, but if you don't have the ForEach command (on OS3, for example), then you could hack it like this (modified it to do what you asked) :P

some paths you want to handle
setenv 1 
"RAM:"
setenv 2 "T:"
setenv 3 "SYS:"

init our counter to zero
echo "" noline ENV:counter

loop start
lab loop

increase counter by one
echo "" >> ENV:counter

read the counter value to a local variable
set i 
`list env:counter lformat "%L"`

; if 
we have a corresponding filethen do stuff and loop
if exists env:$i
   
Get contents
   set p 
`getenv $i`
   ; Do 
stuff
   
echo "Processing $p"
   
if $p eq "SYS:"
      
echo " Special case!"
   
else
      echo 
" Normal case..."
   
endif
   ; 
clear variables
   unsetenv $i
   
unset p
   
jump back in the script
   skip loop back
endif

otherwise clean up and quit
unsetenv counter
unset i


And that would output:
Processing RAM:
 
Normal case...
Processing T:
 
Normal case...
Processing SYS:
 
Special case!

Go to top


Re: how many audio channels are recommended in "AHI"
Just popping in
Just popping in


AHI's mixing routines are quite primitive and if you increase channels, playback quality decreases even if you aren't playing concurrent sounds.

I would advice to set channels as few as you still find comfortable in your use.

I've noticed that I don't use more than two programs that output audio at once pretty much ever, so I've set my channels to two. This still allows me to play something like video clips or test a game while listening music on the background, but keeping the quality quite good.

This is why AHI has the Music Unit, which overrides anything else playing to keep the quality at max in certain cases. But if you want to let everything (including the Music Unit) to play simultanously, you can forward the Music Unit to other unit, but especially in this case I would really keep amount of the channels low.

Go to top



TopTop
(1) 2 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project