Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
157 user(s) are online (116 user(s) are browsing Forums)

Members: 1
Guests: 156

bigmac, more...

Headlines

Forum Index


Board index » All Posts (TetiSoft)




Re: Clockport Ethernet
Just popping in
Just popping in


@agafaster

Quote:

Has anyone ever done (or considered doing) an Ethernet adaptor for the A1200 clockport ?

When there exists a Poseidon driver for USB to Ethernet
adaptors (didnt check that), it should be possible to
attach a Subway USB card to the clockport and the
USB-to-Ethernet adaptor to the Subway.

Go to top


Re: A4000 + OS4 install issue
Just popping in
Just popping in


@Amigaz

When you can see the OS4 bootmenu when pressing
both mouse buttons, you can try if disabling the partitions
on the Fastlane (driver names z3scsi or similar) works around the problem. When you cant enter the OS4 bootmenu, remove the Fastlane and try again.

Go to top


Re: OS4 Problems for classic amiga 1200
Just popping in
Just popping in


@TiredOfLife

Quote:

OS4.0 installed but viewable only on a TV.
Using a Mediator.

No PCI cards found.
Wasn't sure if I was supposed to install the Mediator drivers though.

There exist many flavours of the Mediator which differ
at least in their AutoConfig(TM) IDs. OS4Classic currently
supports Mediator 1200, Mediator 4000 and eventually
Mediator Z-IV. At least the Mediator1200LT is not
detected as a PCI board.

Your description (No PCI cards listed by ShowConfig)
implies that OS4 does not recognize your version of
the Mediator. The Elbox drivers do recognize the board,
so you can try to get it working with them.

See it positive, you dont have to worry about possible
conflicts between OS4 PCI drivers and Elbox PCI drivers
and the Elbox drivers support more cards.
Or see it negative when the Elbox drivers are not stable
yet and you cant display bootmenu on the gfx board.

Go to top


Re: Some questions regarding OS4 for Classic Amigas
Just popping in
Just popping in


@Framiga

OS4 will simply ignore the motherboard FastRAM.

Go to top


Re: Assign command
Just popping in
Just popping in


@Swoop

Quote:

Why do I need to use the path command?

Your icon has "TurboCalc" as default tool. Without path.
Then Workbench will search TurboCalc in the current
directory (where the project file is located) first
and fall back to the search path which is defined by
the Path commands in Startup-Sequence and User-Startup.

When it worked before, either your project file was
located in the same directory as TurboCalc, or your
S-S and U-S defined a search path that included the
directory which contained TurboCalc, or your icons
contained the full path to TurboCalc.

Quote:

Why does the assign command not work without it?


The Assign command is something completely different
than the Path command.

Quote:

Why did my previos assign not work?

It worked. It just did not have any effect on the search path...

Quote:

Why did I get an error message when double-clicking on a project icon?

Because Workbench could not find TurboCalc in the current
directory or in the search path.

Quote:

The only way to get the double-clicking to work, with the
same result as previous OS versions, was to add a path
command, and remove the file from the end of the assign.

Yes. Because it has nothing to do with the Assign command.

Quote:

If an assign is (under OS4) not automatically added to the
path, how is that an improvement?

No need to ask for an improvement. It works as before.

Quote:

The whole point of an assign is that AmigaDOS is aware of
the assignment. Regardless, of whether the assign command
was developed for floppies, its main use is by programs
adding an assign to user-startup when they are installed,
to make the OS aware of where they are located.

Right. Partly. Assigns are not only used for locating
programs but also for locating data. There e.g. exist
FONTS: LOCALE: PRINTERS: CLASSES: HELP: LIBS:

Quote:

If that now doesn't work, without using a second (path)
command it seems a backward step IMO.

There was nothing changed. Ergo no step backward happened.
Even OS3 was smart enough to NOT waste time by searching
a program in FONTS: or LOCALE: ...

Quote:

I am not trying to be a pain. I am just trying to
understand why such a change has been made.

No change happened.

Quote:

If it hasn't been changed, what is the correct syntax
of the assign command, that will correct my error messsage
without requiring the use of the path command.

There exists no possibility to use the Assign command
to change the search path for programs. The Path command
is used to specify the search path. Ok, an indirect possibility
exists, by modifying assigns which are part of the search path.

Go to top


Re: Assign command
Just popping in
Just popping in


@Swoop

Quote:

I can't help but think that this is a backward step in AmigaDOS though.

Previously (3.1, 3.5, 3.9, etc) the following worked:-
Assign TurboCalc: Work2:TurboCal/Turbocalc

Assignments pointing to files are still working in OS4.
The error message comes from the Path command which
does not allow to add files to the path list
(which would not make sense).

Go to top


Re: There is hope for OS4 on the Classic.
Just popping in
Just popping in


@Rob

Quote:

From Elbox's site with regard to all A3/4000 Mediators
Quote:

DMA to A3/4000 motherboard spaceMediator PCI 4000 includes a busmastering controller supporting transfers between PCI cards and the A3/4000 motherboard space.

Can anyone explain what this means. Is it misleading information or is Elbox holding back on certain documentation.

This is IMHO comparable to some IDE cards which are sold
as "RAID controller". Even when the developers claim its
a normal IDE controller with a software RAID driver for
a certain operating system, the marketing guys simply remove
the word "software" from the term "software RAID" because
it sells better...

In this case it seems to be something like a combination
of a hardware PCI busmaster controller plus "software main memory
DMA controller drivers" which require a certain operating
system (AmigaOS, assuming here that there dont exist drivers
for NetBSD or Linux etc).

Go to top


Re: There is hope for OS4 on the Classic.
Just popping in
Just popping in


@TiredOfLife

Quote:

So what would be the downside of using the old Elbox drivers instead of the newer OS4?

The OS4 P96 monitor drivers are loaded as kickstart modules
so the bootmenu and bootshell (when booting without S-S) are
displayed on the gfx board. I dont know if its possible to
load the Elbox drivers and pci.library as kickstart module.
When its not possible, bootmenu and bootshell would appear
on AGA/ECS.

Go to top


Re: There is hope for OS4 on the Classic.
Just popping in
Just popping in


@Catalist

Quote:

My words to Hyperion are, get the DMA access for PCI cards sorted out, this is ridiculous.

What about reading the comments in the compaibility list?
They say
Quote:

No DMA support in PCI hardware

which IMHO perfectly explains that it is a hardware problem,
so please dont blame the software developers for that, thanks.

Go to top


Re: There is hope for OS4 on the Classic.
Just popping in
Just popping in


@Chris

Quote:

I'd like to know if the Squirrel SCSI (PCMCIA) works, and if the 3c589 (3Com PCMCIA Ethernet) driver works.

The 3c589 driver does not work.
The cnet.device driver works.
AFAIK it is unknown if the squirrel driver works, I'm not
aware that somebody tested it. Any betatester with BPPC
and Squirrel here?

Go to top


Re: DefIcons..
Just popping in
Just popping in


@nubechecorre

Quote:

After installing the july update the system doesn't
recognize the lha format and instead of giving to me
the lha icon and launching Unarc when i doubleclick on it,
i have an error message as it is an unknow format..

No idea. When DefIcons is present in WBStartup and the
def_lharc.info file is in ENVARC:Sys/ and it doesnt work,
maybe you broke ENVARC:Sys/deficons.prefs, make a backup
of it and reinstall it from the OS4Final CD to check that.
The July update should have nothing to do with this...

Go to top


Re: DefIcons..
Just popping in
Just popping in


@Chris

You are aware of the fact that its still possible to
store a Disk.info file on a disk so we dont really need
a foolproof default disk icon mechanism for DefIcons?

Maybe a placeholder for a unit number in the default
icon name would make sense, something like def_DF%ld
def_FD%ld def_PC%ld def_USB%ld def_USB%ldC etc. Or
a $ sign instead of %ld.

Go to top


Re: A4 PostScript printing in AmiGS/AmiPDF
Just popping in
Just popping in


@Jack

Quote:

Ok, my fault, the question was intended to read:
how do I make it appear everytime when I get such a dialog
(which is afaik only implemented in amigs/amipdf).
I just keep forgetting it every time...

By clicking the "Save" button in the Settings dialog?
Or do we misunderstand each other here?

Go to top


Re: A4 PostScript printing in AmiGS/AmiPDF
Just popping in
Just popping in


@Jack

Quote:

There is option for postscipt printing in these two applications.
I own a PostScript printer and noticed that using this option is orders of magnitude faster than workbench's postscript driver.
I suppose that Workbench postscript driver prints everything as graphics while Pstscript printing done by passing the file through ghostscript resulting in text and graphics (in case of AmiGS I guess the file comes out from ghoscript unhchanged unless specified in additional arguments).

I guess that the Workbench PostScript printer driver
is able to print both text and graphics, but that AmiPDF/AmiGS are always printing in graphics mode when
using a WB printer driver. To verify that, use printtofile.device as printer port device in the Printer
prefs editor and examine the output file. It should
contain readable text when printing in text mode and
something which looks like a hexdump when printing
in graphics mode.

Quote:

Ghostscript generates pPS document with the same page size attributes as the input, thus "Letter" sized document result in printer complaining about it (I use A4 paper).
I changed default [age size of ghostscript to A4 but additional switch needed to make ghostscript clip the image to the default size: -DFIXEDMEDIA (afair).
the question is: is there a way to make this argument to appear by default inside the print dialog?

A quick look at the AmiPDF settings dialog shows a "Printer" tab with a string gadget to specify the GhostScript parameters.

Quote:

Ability to configure postscript driver for more efficient printing is a good alternative too.

It already supports printing text as text.

Go to top


Re: OS 4.0 Final with update4 HELP
Just popping in
Just popping in


@MamePPCA1

Quote:

@TetiSoft
May I edit BootDevice or BootMenu,kmod.
BootMenu doesn't show any update4 WB partition.
What can I do?

Read Documentation/Kickstart/bootmenu.doc on the OS4Final CD.

For a working dual boot config, you need to edit at least
the KickLayout file and one BootDevice file.

When your update4 WB partition is not shown in bootmenu
but its the bootable partition with the highest boot priority
from where Kickstart/KickLayout and the kickstart modules
are loaded, my best guess is that you created a kickstart
configuration which is missing something really important,
e.g. a driver for your harddisk or the filesystem for your
harddisk. Compare the config with the original from the
update4 kicklayout file.

Go to top


Re: OS 4.0 Final with update4 HELP
Just popping in
Just popping in


@MamePPCA1

All we know yet about your problem is that after loading
the update4 kickstart you see no update4 WB. Please verify
that bootmenu shows the update4 WB partition as default
boot partition, that booting from there without S-S works,
that typing

Set Echo ON
Execute S/Startup-Sequence

after booting without S-S hangs and tell us where it hangs.
You also have the option to capture a serial debug log.

Go to top


Re: OS 4.0 Final with update4 HELP
Just popping in
Just popping in


@MamePPCA1

The SLB will always load the KickLayout file from the
partition with the highest boot priority.

By default OS4 boots from the partition with the highest
boot priority.

bootmenu supports specifying a different boot partition
for WB. The first published version of bootmenu which has
this feature was the version on the OS4Final CD.

You should not use the upd4 kickstart with the final WB
or the final kickstart with the upd4 WB.

Conclusion: The partition with the highest boot priority
needs both kickstarts and the upd4 WB and the BootDevice
entry for final or it cant work.

Go to top


Re: Some questions regarding OS4 for Classic Amigas
Just popping in
Just popping in


@thread

Just realized that the following was not stated yet so I do it:

OS4 for classic Amigas only supports main memory on the
BPPC/CSPPC board (and chip memory on the motherboard).

Things like Zorro memory expansion boards or mainboard
"FastRAM" are not supported. The motherboard memory would
be 16MB max only anyway and slow (from the PPC CPU point
of view), Zorro memory would be probably even slower.

So when you are preparing your classic Amiga for OS4,
populate the PPC board with memory, not the motherboard
(except the 2MB ChipRAM) or Zorro boards.

Go to top


Re: Some questions regarding OS4 for Classic Amigas
Just popping in
Just popping in


@Helge

Quote:

It only seems odd when they praise IDE instead of SCSI.

It seems you misunderstood me. My exact words were
Quote:

the future is IDE/PATA/SATA/USB


Quote:

It is a serious flaw that OS4 doesnt work with SCSI of the BlizzardPPC.

It would be enough if the OS4 devs would only acknowledge this.

I will acknowledge that it is a missing feature.
But not a serious flaw. We are talking about FastSCSI2
with 10MB/sec maximum speed here, this is not so much
faster than the existing IDE solutions.

Just in case we didnt mention it already, it seems there
currently exists no developer who can write that driver,
and there exist more reasons for that than only missing
interest in SCSI. You can continue to praise SCSI instead
of USB2 or FireWire, this may eventually change the opinion
of some people about the missing BPPC SCSI driver from
"missing driver" to "really missed driver", but this alone
is not enough. Did you already ask the BPPC SCSI card
manufacturers for the developer docs for the card or
the source code of the driver or an OS4 port of the driver?
Or did you find existing source code of a driver and a developer
who is interested in porting it?

Quote:

No SCSI, no OS4 for me.

No BPPC SCSI driver without somebody who has the docs,
the skills, the time and the motivation to write it
and the hardware to test it.

Go to top


Re: Some questions regarding OS4 for Classic Amigas
Just popping in
Just popping in


@TMTisFree

Quote:

No SCSI, no OS4 classic.

Thats your summary of this thread, which does not mention
that you simply dont want to use the existing OS4 CSPPC SCSI
driver for your A4kT just because it could ruin your benchmark
results when you attach slow SCSI devices? And you did not answer
if a switched off(!) SCSI scanner is able to slow down an UWSCSI bus.

Go to top



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




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project