@Severin

I might give it a go. Maybe.

Once OS4 is out, there is nothing stopping anyone at all from writing a native blizzardppc scsi driver if they really want to.

@porthan

Yes, but on OS4, both 68k and PPC programs are running on the same (PPC) kernel, so nothing like this is really possible. Trying to use the real 68k on OS4 would make both 68k and PPC programs run slower!

Also, on WarpOS or PowerUP, all the OS functions are 68k and run on the slower processor, but on OS4, all OS calls are PPC native, so system friendly programs get a massive speed boost.

@Ian-uk

I would love it if the SharkPPC came out of retirement. Note, though, that as far as I'm aware, not one person related to OS4 development has access to any kind of prototype, so it certainly wouldn't be any time soon.

@orgin

Yeah. it'll help tide people over, but (IMHO of course), pftp will be a lot better

Progress still continues

Key improvements since my last report:

* Both passive and active transfers are now implimented
* You can pause, resume or cancel any pending or active transfers
* You can transfer whole directories (either just the files, or
all subdirectories and their files too)
* You can delete directories and all their contents
* You can rename files
* You can create directories
* Optional automatic binary/ascii mode selection (based on
filename extension)
* You can save FTP session logs
* Error reporting and handling is much improved


Still to do before I can even call it beta (there will be public beta releases before the stable release):
* Direct FTP to FTP transfers (and also local to local ones)
* Impliment the stats panel of the control window
* Further improvements to error reporting and handling


There is a detailed changelog here.

@Hans

I originally intended to subclass the listbrowser gadget so that I could detect a click and drag out of the edge, but if you subclass the listbrowser, it doesn't smooth scroll any more (probably in case the subclass wants to do some sort of custom rendering that would break the smooth scrolling).

So, I tried adding an IDCMPHook to the window, but you can't trap left mousebutton clicks over the listbrowser. You CAN however trap middle button clicks over it.

For the actual dragging, I opened a borderless toolbar window (the kind that can't get focus), and used ChangeWindowBox() from the same IDCMPHook (using IDCMP_MOUSEMOVE events) to keep it just under the pointer.

@Hans

Drag and drop would be really handy. For PFTP i had to roll my own, and even then had to resort to using the middle mouse button (which is a little counter intuitive, but it works).

@AmiZaP

That is certainly possible, yes.

@AmiGubbe

You select the boot partition via the Early Startup Menu, yes.

Its a little tricky because you have to do it twice (again after the OS3.9 setpatch reboots from cold boot), but it works, and I could avoid it with a little bit of script trickery.

OS3.9 can see all FFS and SFS partitions, but not FFS2.

@AmiGubbe

You can dual boot OS3.9 and OS4. I have both installed on my A4000.

A decent FTP client

Progress continues.

Sending and receiving now works (although only passive mode is implimented so far).

The download/upload manager is starting to work. You can queue downloads and start them later, or add to the queue and start immediately. There is a little icon showing whether a transfer is active, queued or paused.

I started work on drag and drop. I first tried subclassing the listbrowser gadget so that i could detect if the user clicked and dragged out of the side, but if you subclass the listbrowser, it disables smooth scrolling via ScrollRaster() and becomes clunky and horrible.

I then tried IDCMPHook, but you can't get left mousebutton down events over gadgets, they seem to be swallowed up before the hook is invoked.

HOWEVER, I can read middle clicks over gadget, so (for now at least) drag and drop works from the middle mousebutton.

A brief summary of whats already done:
* Sending and receiving
* Modular multithreaded design
* Browse while downloading (if server allows multiple connections)
* Drag and drop
* Multi-window support (although it is as easy and quick to use as a classic 2-pane client, and not as fiddly as most multi-window clients).
* FTP server address book
* FTP session logging

Still to do before I can even call it beta (there will be public beta releases before the stable release):
* Allow to pause or abort current transfers
* Direct FTP to FTP transfers
* Non-passive transfers
* Auto binary/ASCII detection (optional :)
* File management (deleting files, making/deleting directories)
* Transferring whole directories
* Impliment the stats panel of the control window
* Session log saving
* Proper error message requesters

Stuff I intend to do after everything above is done (although not necessarily for the first stable release):
* SFTP
* ARexx port
* Lots of keyboard shortcuts
* Locale support

Another shot (although not very much different to the last one)

God I hate graphical smileys.

Good work, though, jahc, for all those that like the things.

Quote:

Its a ReAction GUI.

@Spirantho

AFAIK, the OS4 kernel doesn't explicitly stop PCI cards on mediator from doing DMA, its just that you can't DMA direct from a card to fastmem. Its just that OS4 doesn't allow you to reserve some gfx card memory as a temporary DMA buffer if you use its native video card driver.

Also AFAIK, the OS4 voodoo driver supports overlay.

@Atheist

They've successfully made an ass of themselves, thrown money away, scammed money out of people, led everyone along in the Amiga community while actually not being interested in AmigaOS, and sold some T-Shirts.

They're very successful at those things.

@mailman

Not really. If you want to use the 100Mbit realtek network card, or an SB128 or SB Live! you'll just have to use Elbox's 68k drivers with pci.library. It still works great.

If you can manage with a 10Mbit network card and no sound card (or a zorro soundcard, or a soundcard that doesn't need DMA), you can use OS4 native drivers. (You don't actually get 100MBit/sec anyway so its not a huge loss for the network side of things).

Its a question of weighing up the pros and cons. Using OS4 native drivers, you might have slightly faster graphics (native gfx card driver), but you have more restrictions on what other cards you can use.

TV cards might work in either case; they DMA to graphics card memory by design.

Work continues... today it transferred its first files

Click for new screenshot

I still have a LONG way to go before it can be even considered beta, but already its multithreaded, and supports simultaneous browsing while downloading (provided the server allows multiple connections).

@mailman

It means that drivers for cards that require DMA will work on AmigaOne (or any future OS4 hardware), but not on classic. Drivers for cards that don't require DMA will work everywhere that OS4 runs.

If you want to use a card that requires DMA, and there is a driver for elbox's pci.library, you can use that instead.

Note, though, that you can't mix and match OS4 and pci.library drivers. You either have to use OS4 drivers *OR* pci.library drivers for your PCI cards.