Who's Online |
56 user(s) are online ( 38 user(s) are browsing Forums)
Members: 1
Guests: 55
328gts,
more...
|
|
|
|
|
Re: Using USB CD Drive with OS4 / X5040
|
Posted on: 2024/6/24 15:28
#101
|
Not too shy to talk 
|
@MartinW
It's possible that may affect it. Though if standard updates have been applied on top it should be fine. Would be good if there was an integrity check of all components above that of doing a simple AmiUpdate.
|
|
|
|
|
|
Re: Using USB CD Drive with OS4 / X5040
|
Posted on: 2024/6/23 13:50
#102
|
Not too shy to talk
|
@MartinW I suppose you're over it now but I noticed your DVD drive came up as unit 0. I wonder if this might mess up the boot process? If it's setup to boot a HDD of unit 0? Usually that was the case. The system does sound a bit flaky if it just crashes like that. Something is wrong there. I have noticed that sometimes if a system component is an incompatible or older version then something will crash. That doesn't look like well programmed software which would use a specific version and fail otherwise. That's what Amiga standard software is expected to do and I expected system software to set an example and hold to that standard tightly. 
Edited by Hypex on 2024/6/24 14:54:07
|
|
|
|
|
|
Re: airprint.device status
|
Posted on: 2024/6/22 13:50
#103
|
Not too shy to talk
|
@skynet Funny. T6: Dark Fate is on tonight. Thought I'd seen it but turns out I haven't. Apparently no ones heard of Skynet.  Anyway in my case I couldn't get AirScan to scan. I tried to print from Wordworth but got the same kind of result as you with the AirPrint window opening up. But I was able to print from AirPrint directly. So what I did was open it up. It gives me SSL errors for some reason. But I was able to open a PDF I had and it printed it. My printer is a simple HP Deskjet 3630 and I had no idea it could accept PDF as that tends to be accepted only by office grade printers or lasers. It supports PCLm which is a PDF variant. However, even though I printed PDF, it's more likely AirPrint took the PDF and had it converted to a compatible raster format for the printer. According to below site URF, JPEG, and PDF are supported over AirPrint. https://openprinting.github.io/driverl ... standards-and-their-pdls/
Edited by Hypex on 2024/6/22 14:25:34
|
|
|
|
|
|
Re: Using USB CD Drive with OS4 / X5040
|
Posted on: 2024/6/22 7:17
#104
|
Not too shy to talk
|
@MartinW An audio CD should show up as data CD with AIFF files. If it doesn't something has gone wrong. As least for a pure audio CD. To play it the audio out jacks need to be connected to the computer or some external stereo system. The drive would be sent a play command and going with what joerg stated it would be an MMC command by the looks of it. This is how things usually worked in a classic Amiga with a CD drive connected internally. It's also how things worked in the XE days with CD audio out connected to sound card. The other way was to read the CDDA data direct from the drive and then play it to an audio device. This method is fine for newer systems with 16 bit audio. But it wasn't as common early on. Later on it became more common. Especially with digital outs and leaving analogue CD outs to be depreciated. It shouldn't matter with ubsdisk.device not sounding CD-like, the same as scsi.device isn't CD like either. It's just a transport device. But I think what does matter is supporting the MMC commands. Given USB uses some SCSI subset of commands it should know more than generic ATA commands. It may or may not help but SYS:Documentation/Kickstart/CDFileSystem.doc does give you some keys you can press on CD insert:
Supported qualifiers (press when inserting the CD):
- <ctrl>: Disables data track on mixed audio+data CDs,
mounts HFS/HFS+ instead of ISO 9660 on hybrid CDs.
- <shift>: Disables audio tracks on mixed audio+data CDs.
|
|
|
|
|
|
Re: airprint.device status
|
Posted on: 2024/6/18 2:17
#105
|
Not too shy to talk
|
@skynet
Did you try from the AirPrint app? Or just another app doing normal printout?
|
|
|
|
|
|
Re: airprint.device status
|
Posted on: 2024/6/16 5:49
#106
|
Not too shy to talk
|
@pvanni Quote: if I remember right, Turboprint comes with a PS: device that invoke gs with the selected printer driver. In the Turboprint prefs there is a PS tab with the command to print when some program write on the PS: device It does comes with a PS interpreter. I suppose this is for programs printing as PS format which are then converted by the printer driver. Unless printing as PS document is useful I thought just using a direct driver would be best. It's still updated for Linux. I don't know how up to date the driver are but it's still newer than the Amiga version. The Amiga version cost 30 euros more. Strange situation. Technically they still support the Amiga as they still sell it. But it looks like abandon ware as the newest printers supported are about 15 years old.
|
|
|
|
|
|
Re: airprint.device status
|
Posted on: 2024/6/14 14:06
#107
|
Not too shy to talk
|
@Tuvok First, lol. Good one. He is also one of my favourite characters.  Quote: That PSPRT: device would have been great! Thanks. Yes would have. Suppose I could still look into it. Quote: What do mean by "backwards"? Is it because when adding a new printer, one has to put a printer driver in DEVS:Printers first, and will then be able to use the printer, instead of having an "add printer" GUI that lets you first select a "bonjour" printer and then select the appropriate driver? Yeah, pretty much, but even going deeper. So these days, when you add a printer, using USB as an example, you plug it in and the printer is auto detected. A dialog comes up and it determines the driver for the printer and activates it for you. Usually downloading it. Now, if we take the net out of it, we can even use examples like Windows where it does the same but looked for drivers on the Windows disc, or another disc inserted. On AmigaOS, not only is the design old, but it comes with a limited subset of drivers. Ancient really. They've removed some newer stuff from OS4 but left all the older drivers in. Has anyone really connected an MPS1250 EpsonX in IBM mode to an OS4 machine in the last 20 years?  Quote: Regarding the very old printer system, how should a concept for a new printer system look like? I'd start with the user experience. Now not much can be done about the drivers. But it would be good if a generic GDI or PCLGUI driver was offered. Something that updates the drivers to printers in this century. HP even have sources for their drivers that I've looked into retrofitting into the existing HP_CYMK Amiga driver code. Drivers aside, a daemon of sorts that picks up USB devices would be good, which already exists for storage devices so detecting printers should be just as possible. Even without that, Printer Prefs could scan for a printer over various transport layers, display a list to pick from and suggested driver. Or select one to activate and copy in if needed. But leave out parallel.device, usbprinter.device and all that technical stuff. It's called a user interface, not a developer interface. They need to shake that off. Another backwards step, going from a user oriented OS to a developer oriented OS. No user should need or know what device driver API to use. Forcing users to learn programming terms is a red flag you are programming the OS wrong. Even Linux wouldn't do that on the desktop surface level Quote: Maybe adopting CUPS will be the easiest way? [OT]Btw, Is there any OS4 development going on anyway? And wasn't an update to the Enhancer software supposed to be released around 2023 christmas time or first quarter 2024?[/OT] That's been suggested in the past. The problem is CUPS is designed for a different OS driver API system. Though, by contrast, AHI does have some Linux based drivers used as basis for AHI driver. So there is the printer API and then the driver API. A device API using library API for drivers. Either printer API would need to be wrapped around CUPS core and drivers. Or drivers would need adapting with CUPS driver code to work with native printer API. Best would be broad drivers to cover a range of models. Such as broad HP drivers that can drive a broad range of printers. Of course, the driver being able to communicate with the printer, so it could determine model and features would be good to configure a run time driver model adapting itself when loaded. One thing I will say needed is jobs. The printer API and clients have no concept of print jobs. I touched on this earlier. Given you've got old programs (or new) that write random data to the printer API, it would be hard to add that concept. By random I mean a reset command or writing lines out at a time. There's nothing for starting and stopping a page. Even opening and closing the printer device won't do it, as that can happen, while a program writes different data to the printer in one session. OS4 development is still happening. Just not in the printer department. Enhancer had some update in August 2022 and another is due this year. Quote: On the other hand, if AirPrint.device is going to work "driverless" that would solve most problems, right? For drivers it would, yes. Of course, driverless is a fallacy really, since there is still data that needs encoding in a specific format. Given it could be PDF or JPEG or URF makes no difference really, as it's still a data format. But being a common format that can be generated easier does make a difference. IPP over USB would be good. But since my printer is on the network, I can still reach it from my X1000. Quote: AFAIK the OS4.1FE printer system is on par with the OS3.2.2.1 one, so it is not limited to 4096 Colors anymore? No I certainly hope not. 1985 wants its colours back. Ha. IIRC it's been 24 bit since OS3.9 and OS3.1 on AGA should have fixed that.
Edited by Hypex on 2024/6/15 15:23:14
|
|
|
|
|
|
Re: airprint.device status
|
Posted on: 2024/6/13 5:36
#108
|
Not too shy to talk
|
@mcleppa Quote: Yes, this is due to my program supports only ipp at the moment, this is due to this protocol is well documented and is the best chance to support as many printers as possible. Most printers you buy today supports this protocol. Ok I understand now. Needed to refresh my memory. I was aware there was a LPR driver but I don't recall testing it as my X1000 is connected to my printer over USB. Quote: When finished and program is working fine with this protocol, I might add support for the other kanguages as well. So checked and my printer supports PCLm and ARF. PCLm looks interesting as it's some kind of PDF format. So apparently my printer is better than I thought it was for a budget home model. Quote: Yes, most new printers does not support direct ascii printing trough ipp, but most of them support raw printing still. So I can dump text to printers trough the raw printing port, if sending text trough ipp I need to convert to rasterfile first. I had read about that years ago. I'm sure my HP does support it. But that is not through network so not relevant to IPP in this case. Quote: You are right in that converting text to graphics require a lot of information of fonts used etc.. And f.ex printing from notepad I haven’t found a way to retrieve font information. So my plan is to just use a predefined font and size at the moment. I am using IntuitionText for converting to bitmap, which makes the work easier for me. To my knowledge NotePad would just dump text to the printer through the driver. You could likely find out by extracting it from the prefs file it uses. But that limits it to NotePad only so other text editors printing won't use it. There's ways to find default font. I know the non-proportional default font is in GfxBase->DefaultFont after asking around, which is used by the CLI. IntuitionText is probably the best way. I've used that to grab text sizes when calculating a layout. Text() function could be more direct but Gfx is made for bitplanes while Intuition can be used for pixmaps transparently. It can also provide a default font. But for single colour printing a bitmap may actually help. If PCLm supported basic text you could have just encapsulated it inside a basic PDF, but it looks like it has the same raster limitation. Quote: Most ipp printers I have used, does not support PS, but the formats they usually support is pwg-raster and jpeg formats. PS would have been accepted by earlier printers over direct connection. IIRC PS was supported before PDF. As PS was suited for being a printer PDL while PDF was suited to viewing documents on screen. Quote: If GS this is updated trough enhancer that would be great, and then I probably haven’t installed it, because my version of GS sometimes fails converting pdf’s. That would create a dependence on Enhancer but these days some OS components in the OS4.0 days are now depreciated and moved into Enhancer from OS4.1. Quote: When testing and prigramming this printer device this is for me what looks like is happening:When printing from AmiPDF or AmiGS it sends command to GS trough amiga_printer device of GS and communicates trough Exec msg, GS creates graphics trough printer.device which then again is sent to the selecter printer driver. This driver decides what to do with with the graphics, in my case it is converted to raster format, this will then be transferred to a new device, in my case airprint.device this device sends it to printer in the correct format. Ah yes, I recall using AmiPS and AmiGS to print. They aren't very well integrated in the OS. Well, an add on really. The Amiga printer system is very old. It works backwards to how things work today, as you need to manually select and install the driver. And the printer device API has no concept of what print job is. I found this out when developing my HP_Photosmart driver based on the HP printer source. I had to work around it somehow as clients tended to send discrete dumps to the printer device, so most printouts were writes of various data. It's going back years but I recall some things about AmiGS/AmiPDF and just checked then to refresh myself. So you could chose Workbench driver or custom driver and direct device. Workbench driver would go through printer device but other drivers which included PS, PDF, images and specific printers are sent to DOS device. It defaulted to PAR: but that was rather obsolete by then. PAR was old, lol. I had some alternate called USBPRT: or something that diverted to usbprinter.device. So it sent it to the printer direct as possible without involving printer device. A NETPRT: or AIRPRT: could be conceived in the same way. AmiGS and AmiPDF are really just facades for the ghostsscript command. The way they work is rather sloppy as they invoke a CLI command to do their dirty work. That may be acceptable on an OS like Linux where it lives on CLI commands, since it wasn't designed as a desktop OS; but AmigaOS is more integrated like Windows, and there should be a library acting as driver to handle it. It was a bit of a hack and the interface was messy with needing to deal with old DOS devices. For a number of years I wanted to write a PSPRT: DOS driver. This would have accepted PS as input but would have rasterized the output to a non-PS printer. So it would be a PS to PRT converter you could say using printer device. It would have used ghostsscript command to convert PS to a raster so would have been a bit of a hack in the same way. But I never got around to it. A few word processors could output PS and there is the Workbench PS driver. So it looks like my printer supports stripped-PDF. That's useful, but still not much sends PDF on Amiga, so would need converting from graphics to PDF I would think.
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 2024/6/12 14:48
#109
|
Not too shy to talk
|
@MamePPCA1
That doesn't sound like a good omen. Giving it 7 years and say it will die. That's not how you give your customers confidence!
If your X5000 still works the hardware should still be good. But RAM, cables and HDD can degrade. Dust can accumulate. In particular RAM sticks can collect micro-grime just sitting there. Even just pulling them out and back in can help. Otherwise removing and cleaning the contacts can be good. I replaced the RAM and SATA cables in my X1000 when I saw signs of instability like crashing on boot. After replacing the battery.
While I don't think the X5000 is dying just yet, 7 years is a long enough time for mechanical wear on a harddrive. Be good to check the smart log for any issues. But OS4 only has a smartmontools command I know so having Linux with a GUI is just easier.
So you have Enhancer on CD and that should be a way you can get access to your files again. In the least it should have a working SmartFilesystem and PartitionWizard. You could try copying files or installing. Best to backup pendrive on another computer as a full image backup just in case.
SmartFilesystem should be easily found in the installation files under Kickstart drawer on CD. Then just copy over the top of the existing one. On the pendrive.
Another way, and this may be easier, is to simply install Enhancer on the pendrive. You may need to do more clicking off for options you don't need if you just want to update Kickstart. Or you can just install most or all to pendrive.
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 2024/6/10 11:24
#110
|
Not too shy to talk
|
@MamePPCA1 If you cannot format your DH0. From your pendrive Workbench. Then it's unlikely to help you see your other volumes. In the case you could reformat and install OS4 fresh, I can only see you being able to boot from a fresh Workbench off HDD. But still not able to see your other partitions. Do you have Enhancer on CD? It's likely this could also come down to a few trivial files needing to be in the right place. But having those right files and installing them in the right place is proving difficult. I agree with daveyw here, there's only so much advice we can give remotely. And I should stop replying before I kept repeating myself.
|
|
|
|
|
|
Re: airprint.device status
|
Posted on: 2024/6/10 10:29
#111
|
Not too shy to talk
|
@mcleppa Just found this project. Quote: Should work with almost all network printers. But not usb printers. Why is that? Not because of connection but supported languages? I have a HP Deskjet 3630. It's connected to my wifi network so is technically a network printer. But it's also an AIO home printer that only supports PCL3GUI and not PS or PDF like an office printer. Quote: As mentioned in another post, printer.device use a gs interpreter which is old so I need to update this one with a newer version. Well, what ever it is based on, the PS interpreter is just a driver. And most printers need direct PS support or they won't work. As for GS in OS4, I'm not aware of printer.device using it, it was external AFAIK? A newer version should be installed with AmiPS and AmiPDF from Enhancer. Quote: Still working on converting raw text to graphics, so this is not finished. Is this because the printers don't support ASCII any more? In that case it's out of your hands really. It's not your job to convert ASCII into a printer raster, that's a lot of work needing fonts used and all sorts of technical details. Unless doing very basic printing most people would be printing documents which are all graphics. Suppose you could just render a bitmap in the default proportional font and dump that to the printer.
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 2024/6/9 10:14
#112
|
Not too shy to talk
|
@MamePPCA1 You don't need to use SFS/02 unless you want to format and erase your data. But even then I don't think Workbench needs SFS/02. It's only needed if you need 64 bit support. And it's risky as there are no recovery tools if it goes bad. Another possibility is if the volume has an error it may refuse to mount. According to the table below SFS/02 has no recovery tools. For this reason is why I just use SFS/01 on my Workbenches. Mine are just 4GB in size so don't exactly need 64 bit any way. Another possibility would be to install OS4 to a new pendrive partition or even another USB stick if you had a spare. Slow for sure. But okay for emergency Workbench. https://wiki.amigaos.net/wiki/UserDoc:AmigaOS_File_Systems
|
|
|
|
|
|
Re: A1222 Freezes when writing to the RAM DISK
|
Posted on: 2024/6/8 15:05
#113
|
Not too shy to talk
|
@Maijestro Quote: Under Qemu/Peg2 I never had problems with copying to the ram disk until the memory was completely used up. Re Yes, I bet that it would have given a practical out of memory error or some such. For some reason they thought it would be better to replace this perfectly fine working system with one that freezes the hardware instead. Developers have strange ideas on what they think is user friendliness. I don't know how developers even think that is better if they have actually tested the implementation for real. It's fine if it works but if it doesn't work there isn't much point replacing a limitation with a hard crash caused by a software fault. When you have 2GB of physical memory addressable by the OS there is no reason why it cannot load 600MB of data into RAM. How much memory is the OS using?
|
|
|
|
|
|
Re: FTP Between OS3 and OS4
|
Posted on: 2024/6/8 13:31
#114
|
Not too shy to talk
|
@Hans Quote: Officially, FTP has no UNIX underpinnings. However, the specification's LIST command is very ambiguous, and so UNIX servers used "ls -l" format. Eventually, this got so common that it became the de-facto standard. That would explain it then. It is hidden well within a GUI. And not noticeable using a HTTP FTP server. Quote: The MLSD command in the RFC 3659 extension does it properly, and supposed to replace LIST. However, being an extension, not all clients or servers support it. It's on the ZitaFTP Server to-do list... After looking it up much of the info about MLSD is about server time outs. Surprisingly a lot of shared info about FTP commands doesn't give any details on how to use it. Is this such accumulated knowledge that every IT person is expected to know the format of every FTP command off by heart? Well, description part of a file looks closest to a comment. I thought comment was a common way of describing a comment, rather like dialog has become a common word, but it seems comments are still hard to find. Though having said that the Linux desktop gives no options for setting file comments. Surprised it's that basic.
|
|
|
|
|
|
FS-UAE OS4 boot freeze
|
Posted on: 2024/6/8 5:51
#115
|
Not too shy to talk
|
Hi guys.
So I've had this random issue for a while. I set up OS4 emulation in FS-UAE running on Linux Mint Una. But sometimes when booting to Workbench it displays the boot logo for a short while then goes black and sits there.
I tried booting to a shell and running startup. It was able to do that. FS-UAE does seem stubborn when I need to get to early startup though. Takes it 5 times on average to respond to both mouse buttons. For some reason it likes it ignore them. I don't know if FS-UAE or Linux has an issue with detecting mouse buttons.
But sometimes and too many times when booting normally it gets to the point of loading Workbench, blanks the boot logo, then just stalls. Does anyone else see this? Is this a common glitch?
FS-UAE Launcher 3.1.67
FS-UAE 3.1.64
QEMU-UAE 3.8.9
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 2024/6/8 5:23
#116
|
Not too shy to talk
|
@MamePPCA1 MediaToolBox would be able to tell you if it lets you select USB as controller. It usually does on start. I just looked up details of SmartFileSystem in Enhancer and the page lists how to specify 64 bit for SFS\02. I just use 32 bit SFS\01 for my Workbench. The 64 bit one is risky as it had no recovery toolss. The other thing I mentioned was the Mass Storage Commodity. This usually runs from wBStartup. By default it's enabled on Workbench. If it's running this can be easier. With a USB key inserted just press the key combo which is Ctrl Alt M. A window should pop up with USB devices and file systems listed. Apart from that using Find (Amiga F) you can use it to search for SmartFileSystem on the system. Click on any found and press Amiga N for Info to open up Info window. Now press Version to see version if that file. If you had an Enhancer CD you could have just replaced it on pendrive. https://wiki.amiga.org/index.php/SmartFileSystem
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 2024/6/3 13:23
#117
|
Not too shy to talk
|
@daveyw
It could just be a standard SFS as included on install CD. But one that is incompatible with X5000 as smf pointed out as being unsupported.
Even so, Kickstart can still boot off HDD, that had booted WB. So, SFS should still be available and loadable. Just by letting Kickstart load off HDD and selecting USB drive from boot menu. But of course, AmigaDOS would need to pick up USB drive for this to work. I should test if that actually works but I don't know if that works on an X5000.
|
|
|
|
|
|
Re: Tracing of callhookpkt()/callhook()
|
Posted on: 2024/6/3 6:21
#118
|
Not too shy to talk
|
@kas1e Quote: Do some debugging with GDB and find out that even for IUtility->CallHook(.....) there seems to be 68k emulator check too (while, it different functions still, and not simple use of CallHookPkt() inside), see: How did you do that? The only GDB I know working is the old 6.3 one and being they can all report same build date makes it hard to know which. And it only works on A1/XE and Classic from my testing. Quote: And as far as i aware, this function checks whether a pointer points to a segment containing PPC-native or 68k code. The segment is determined by the most significant 4 bits of the address, which is then used as an index into a table. The type read from this table is 0 for 68k code and 1 for PPC code. When a 2 is read, then the BAT registers decide about the type of code and go back to callhook(). Except there's some slight overhead manually checking like that. It's true PPC and 68K would be in their own segment. I don't recall where but I read that 68K and and PPC spaces are marked by MMU. May have been in some document on porting libraries. So what it does is attempt to simply jump to an address. If it's not marked as executable segment it will cause an ISI trap. The trap will check the address and if it's 68K drop into the emulator to run it. That allows code to run transparently without checking addresses like a standard emulator would. But, for calling hooks, it could just check before jumping in. From native code it should be native. But I suppose hooks are backwards compatible to 68K as well. Quote: Exactly the same code present in the CallHookPkt() too, so they both seems to call some internal function which do that check, something like "is_hal_native()" or something of that sort. There is something. I forget which. It may be TypeOfMem() but that was also around in 68K so not specific to OS4 checking address is 68K.
|
|
|
|
|
|
Re: Tracing of callhookpkt()/callhook()
|
Posted on: 2024/6/3 5:58
#119
|
Not too shy to talk
|
@joerg Quote: For AmigaOS, 1-3.x/m68k and 4.x/PPC, it's useless, the REG(), ASM, SAVEDS, etc. macros are enough if you want to support both m68k and PPC versions of AmigaOS, or even just different compilers: SAS/C, DICE, StormC, VBCC and GCC for m68k AmigaOS, VBCC and GCC for PPC AmigaOS. SDI is only required if you additionally want to support AmigaOS incompatible OSes like AROS and/or MorphOS. I thought it was useful for any cross Amiga development. Including modern development. Especially for AROS and MOS without major changes. Quote: Standard Developver Interface Thanks. So it wasn't anyones initials. Now if only they stated this on Github. :[-D
|
|
|
|
|
|
Re: AmigaOS 4.1 Final Edition Update 2 fatal failure
|
Posted on: 2024/6/2 15:14
#120
|
Not too shy to talk
|
@MamePPCA1
Now I'm curious. What filesystem is the pendrive in? FFS would be most compatible but I wonder what it is. You can use MediaToolbox. Or Ctrl-Alt-M key combo on Workbench should bring up Mass Storage Commodity which will list USB filesystems.
|
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
