Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
74 user(s) are online (50 user(s) are browsing Forums)

Members: 1
Guests: 73

Futaura, more...

Headlines

Forum Index


Board index » All Posts (salass00)




Re: power managment and gfx cards discussion
Just can't stay away
Just can't stay away


I added A1222/X5000 DMA support to graphics.library in January 2022 (versions 54.250/54.251). In order to work it also needs a newer kernel for the fsldma.resource (if a too old kernel is detected the DMA support code is not used).

Go to top


Re: AmiUpdate unarchiver question
Just can't stay away
Just can't stay away


@Raziel

The PKWARE zip archive format supports several compression methods including zlib (AKA deflate), bzip2, lzma, xz and zstd.

Traditionally zip archives only use zlib compression though, and zip archives that use more advanced methods are generally referred to as zipx archives even though the file format is the same.

The xadmaster.library zip client supports only zlib method but Archiver has it's own zip client that makes use of zip.library which has support for other compression methods, as well as being able to create/modify zip archives and not just read from them.

Go to top


Re: Latest DOSBOX : with PPC dynamic recompiler and stuff , right there!
Just can't stay away
Just can't stay away


@SinanSam460

__lwbrx() sounds like it's an inline assembler function based on the lwbrx instruction. If so, you should be able to replace this instance with:

entriesDataSize = __builtin_bswap32(entriesDataSize);

assuming that you are using a new enough gcc.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@joerg

I am aware of those functions as they were based on ones I use in my filesysbox. A couple of functions for decoding and encoding UTF-8 characters (that programmers can choose to use or not) does not mean that the OS supports UTF-8 though.

Decoding and encoding UTF-8 sequences has never been a problem on AmigaOS really (even before utility.library support there were several 3rd party libraries available for this, as well as the functions in newlib).

The most important thing that is missing IMO is that there is no way to actually render UTF-8 or unicode using the standard graphics.library text functions. The only way to do so currently is to ignore graphics.library and use the low level bullet interface directly which is really tedious and doesn't work well as a general solution for applications. Until this is solved there is no point in trying to use UTF-8 in locale catalogs as those characters will not render correctly in pretty much any applications at all.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@joerg

AmigaOS does not support UTF-8 and that is unlikely to change any time soon.

Should a miracle happen and this situation changes at some point it is just a matter of removing/commenting out a line in the filesysbox makefile to disable the UTF-8 to/from local charset conversion.

Unlike the old attempt at charset conversion this one:
1. Queries what charset is used on the system and uses the unicode maptable for that charset.
2. Unicode values that can't be converted into the local charset are converted into base32 escape sequences that can be converted back into the original UTF-8.
3. Conversion only happens when strings are passed between AmigaDOS and filesysbox. Internally filesysbox uses only UTF-8 file names.

I implemented it because I got tired of literally everyone's initial reaction to trying a FUSE file system being to ask why it doesn't handle UTF-8 characters, even though it handles them just fine (just nothing else did or does).

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@FlynnTheAvatar

Quote:

If I understand correctly, FileSysbox should handle the translation from UTF-8 to the local (latin-1) charset. Does this also work on AmigaOS 4?

I have a share with some non latin-1 chars (music files) that only works correctly with smbfs (the old one) on AmigaOS 4. Both ssh2-handler and smb2fs-handler cannot handle the UTF-8 filenames.

Filesnames are correct with the latest filesysbox and smb2-handler on my Amiga with a 68020 and AmigaOS 3.2.1.

Filesysbox.library has the version 54.9 on my Amiga X5000.


For AmigaOS 4 charset conversion was added in version 54.12 of filesysbox.library that was released to beta testers only just under two weeks ago (6.1.2023).

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@trgswe

Quote:

...i have the active=1 in the tooltypes but when booting the
samba share isn't mounted and can't be mounted either


When you say "booting" do you mean that you have it auto-mounted from DEVS:DOSDrivers? If so it will not work because this is too early and there is no usable network connection yet.

Maybe in a later version I will make it keep trying every x seconds to connect if it fails the first time, but right now it only makes one attempt at connecting to the share and if that fails it gives up.

To get more information on why it is failing you have to capture the serial debug output using sashimi/dumpdebugbuffer or a null-modem cable.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@pvanni

No, not yet. The reason is that smb2-handler doesn't support either utime() or utimens() FUSE operations as I have not find a way to implement them using libsmb2.

As a result any call to IDOS->SetDate() will result in ERROR_ACTION_NOT_KNOWN.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


Smb2-handler uses regular gethostbyname() from bsdsocket.library to resolve the host name into an IP address (same as ssh2-handler).

To avoid having to use IP addresses I have on my computers in DEVS:Internet/hosts (/etc/hosts on linux) the host names and corresponding static IP addresses of machines on my local network.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@trgswe

Quote:

yes, but you might have to install samba 1.0/CIFS or/and samba
direct feature from the control-panel/programs/turn windows
feature on or off, you might have to use password/user since
windows 10/11 does not allow guest access to shares under certain
circumstances


Definitely no need to do this for smb2-handler (only the ancient smbfs needs it). Libsmb2 has zero support for the old and insecure SMBv1/CIFS protocol (only SMBv2/v3 are supported).

That being said the current AmigaOS port of libsmb2 is limited to NTLMSSP authentication only (not sure if this is a problem) as it is built without libkrb5.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@tekmage

The total blocks count is too large for id_NumBlocks. Try this version and report if it works better:

https://www.dropbox.com/s/t6nzkjocs7u870h/smb2fs-20230104.7z?dl=0

The reported fs block size will be larger than it actually is with this version, but the used/free percentages should at least be reasonably correct.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@tekmage

Can you run smb2-statvfs-sync against your samba shares and report what it outputs?

You can get the program here:
https://www.dropbox.com/s/1tcz1xnoypj7ulg/smb2-statvfs-sync.7z?dl=0

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@BSzili

You're welcome.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@BSzili

There is something wrong in smb2-handler as well in that smb2_rmdir() returns success (zero) even though it did nothing.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@BSzili

Not sure what you mean. That is how deleting normally works in AmigaDOS (and Linux too) if you call Delete() on a non-empty directory it fails with ERROR_DIRECTORY_NOT_EMPTY/ENOTEMPTY. In order to delete a directory with contents you have to recursively delete the contents first and only then delete the directory (if you use the WB delete function it does this behind the scenes, if you use delete command you have to use the ALL switch).

I just tried using WB to delete a couple of directories over smb2-handler on my AmigaOS 4.1 FE update 2 system and it worked just fine (I also checked on the Ubuntu host and the directories really were deleted).

That being said if whatever method you are using to delete using relies on IoErr() returning specifically ERROR_DIRECTORY_NOT_EMPTY after Delete(dirname) then that won't work with the current smb2-handler.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@Spectre660

smb2-handler V53.2 is now available which maybe fixes your problems:

https://github.com/salass00/smb2fs/releases

The libsmb2 rename function was previously missing code to convert the path separators ('/' to '\') in the destination path.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@salass00

Quote:

...while testing the rename function I did find a bug in filesysbox in that it doesn't allow to rename a file if the only change is in the letter case of the file name (f.i. "rename tmp TMP") and the underlying file system is case insensitive. Also if the rename is a no-op it should return success (currently it returns ERROR_OBJECT_EXISTS).


These two bugs are now fixed in filesysbox V54.11.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@Spectre660

Quote:

Renaming the file works just fine here both from WB and from shell.

I was initially a little confused why the tab completion wouldn't find the file, but then I realized that the problem was because I had 'Show .info files' unchecked in the shell settings.

Quote:

With the other issue I get (-1) Error -1 when trying to move the files between directories .


Moving/renaming from one dir to another works fine for me also.

What OS is the Samba share that you are using running on?

The -1 error suggests that it is the smb2_rename() function that is failing.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@Ami603

Quote:

In the meanwhile i've noticed that i cannot create files/drawers with some spanish/french characters from AmigaOS4 to my NAS.


You will find this is a problem common to all filesysbox filesystems and is because filesysbox supports/uses only utf-8 file names.

In order to properly convert file names between utf-8 and whatever local 8-bit charset AmigaOS is configured to use there would have to be some method of encoding/escaping the utf-8 characters that have no local charset equivalent that ideally doesn't run into false positives or use too many special characters (so you get problems with pattern matching). Even with a relatively efficient scheme a utf-8 character could end up taking between 4 to 6 characters which to me is rather impractical.

Go to top


Re: AmigaOS port of libsmb2
Just can't stay away
Just can't stay away


@Spectre660

rename 7500.Last.TCD.info 7501.Last.TCD.info

works just fine here.

Go to top



TopTop
(1) 2 3 4 ... 91 »




Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project