Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: bakoulis on June 17, 2007, 10:57:09 PM
-
Hallo Amigans
Please I need some help. I had used an older version of fblit to my A1200/04 Os3.9 to the past. It was buggie for me and I had disabled it. To day I'd give a try again and enabled it but again I'm not happy. So, I'd look for a newer version to aminet maybe better and without many bugs.
I found the newest fblit (3.79a) downloaded, installed and....don't run at all!!! Yes, When executed from startup-seq returns "file is not executable"! Same think when executed later to a shell window. When hit the icon from WB seems to loaded but I don't think is really works. In any case the fblit must loaded after blindriver command and before the next commands for better results. So if don't load from startup-seq is useless. Have anybody the same problem? :-?
________
SYNTHETIC WEED (http://syntheticweed.org)
-
Can't say I've had such problems, older FBlit though... But I do recall that it comes early in the startup-seq, well before BindDrivers.
-
meega wrote:
Can't say I've had such problems, older FBlit though... But I do recall that it comes early in the startup-seq, well before BindDrivers.
yes, yes my fault before blinddrivers. But this isn't really big problem. The command "c:fblit" returns "file is not executable". Is strange, 5 mins before installed the new version check the older and works. The new version don't. So, maybe the file from aminet is corrupted. Can anybody download and test it? :idea:
________
FREE FUCKTUBE (http://www.fucktube.com/)
-
I use fblit here, plus ftext. Some problems with some old apps (speccially with non RTG-able ones).
But is easy to find if the program is running or not: run fblitgui (it is in the packet, if I remember right).
Maybe I'm wrong, but Fblit don't run in Miggys with non-funcional MMU (<030 cpus, including EC ones).
-
rkauer wrote:
I use fblit here, plus ftext. Some problems with some old apps (speccially with non RTG-able ones).
But is easy to find if the program is running or not: run fblitgui (it is in the packet, if I remember right).
Maybe I'm wrong, but Fblit don't run in Miggys with non-funcional MMU (<030 cpus, including EC ones).
Fblit don't load at all for me. Same the fblitgui the program returns the message "file in not executable"
My amiga have 040/25MHz and fblib runs normally on anything 68020+
I told you the old version runs to my system, the new don't run. Can you download and test it from aminet?
If it runs for you, please give me a link with the working file. :-D
________
COLORADO MEDICAL MARIJUANA DISPENSARIES (http://colorado.dispensaries.org/)
-
Are the file protection bits correct?
-
meega wrote:
Are the file protection bits correct?
I'm not sure how is the correct and how the fault.
Can anyone look that file? http://de5.aminet.net/util/boot/fblit.lha
I'm a stupid and the program is O.K.? or is corrupted?
________
Sardinian cooking (http://www.cooking-chef.com/sardinian/)
-
Select the FBlit program's icon, and choose Information from the Icons menu, and check that the e (executable) bit is set/checked/on.
If it is not set on, then set it in the Information window and save, or type:
Protect C:FBlit +e
into a shell/cli.
(Standard arrangement of set bits is rwed, for an executable binary.)
-
May be a stupid question but you definatly have them in the workbench:C/ directory dont u!!
-
@foleyjo
If it wasn't in the path somewhere (e.g. C:) then he would be getting "Unknown command", not an error that it is not executable. Meega is correct - the OP just needs to use the protect command to make it executable. I suspect the programme was transferred on an MSDOS floppy disk so has lost its protection bits.
--
moto
-
Did you try to check the 'executable' mark in the tooltypes of the Fblit icon ?
-
motorollin wrote:
@foleyjo
If it wasn't in the path somewhere (e.g. C:) then he would be getting "Unknown command", not an error that it is not executable. Meega is correct - the OP just needs to use the protect command to make it executable. I suspect the programme was transferred on an MSDOS floppy disk so has lost its protection bits.
--
moto
The program transfered into a usb stick to my amiga, but compressed into LHA file, so the protection don't change from aminet to my harddisk.
The problem was really the protection, I give: "Protect C:FBlit +e" in a shell and the problem gone.
Nobody downloaded the fblit from aminet the last years?
I belive the file have wrong protection by the author. Check it your self, the link have sent to a previus post. Thanks all guys who sent an answer.
:-D
________
NEW JERSEY MEDICAL MARIJUANA DISPENSARIES (http://newjersey.dispensaries.org/)
-
Nobody downloaded the fblit from aminet the last years?
Probably many have, but I guess protection bits are so obvious for all of them they didn't have to think twice.
-
Piru wrote:
Nobody downloaded the fblit from aminet the last years?
Probably many have, but I guess protection bits are so obvious for all of them they didn't have to think twice.
Yes, ofcourse the world is full of genius! And our community have plendy. Never mind, now you have a stupid member, me! :lol:
________
VIDEO REVIEW (http://videoreviews.org)
-
Excellent, you have solved it. :-)
Protection bits are not necessarily preserved correctly in archives. It used to be standard practice to check that any executable files were actually set as such when you extracted your files from the archive. Readme files often told the user which files to check.
-
meega wrote:
Excellent, you have solved it. :-)
Protection bits are not necessarily preserved correctly in archives. It used to be standard practice to check that any executable files were actually set as such when you extracted your files from the archive. Readme files often told the user which files to check.
What I say? Maybe you have right. I have tested millions lhas but this happened to me first time. Thank you for your help :-)
________
Amateur Tube Videos (http://www.fucktube.com/)
-
bakoulis wrote:
What I say?
You said:
bakoulis wrote:
The problem was really the protection, I give: "Protect C:FBlit +e" in a shell and the problem gone.
Solved.
Edit: and a very satisfying (for me) 290th post.