Some assistance is needed.....

[pyrre]

#1 I struggle with my IndivisionECS.
- I empty the dev:monitor/ folder and the computer boots up with colors and working quite nice. in low resolution though.
- The problem occurs when i change ANY screenmode settings. The main WB screen goes into black and white. other screens show colors. dopus i in full color mode, if 16 colors are selected.
- But no matter what other screenmodes i change to, WB screen goes black'n white.
- HighGFX mode does not seem to do any changes. putting the screenmote in monitors does nothing. no new screenmodes to select. and the only file present in the "devs:monitors/" is the highGFX screenmde files.
- Should i put other files there or make any entries to the startup-sequnce?

#2 I struggle getting my buddha finding CF cards. i have an old 500MB HDD that works...... Well... it works....
- I try adding cf adapter to the same cable, changing between M/S. putting the disk and the cf on separate channels, no identifying. all though when HDToolbox scans the controller the cf adapter blinks when it scans unit 5 in the scsi chain.
- Oh. and putting the icon tooltype to "buddha_atapi.device" the HDD does not show up. By just using "ASKDEVICE" in icon tooltype the HDD shows up and i can partition and format it without problems...:eek:
- i use a SanDisk ultra 4GB CF card, and i have multiple adapters. and no avail... no results. though, i can addres it in uae, even partirion and format it. but it does not show up in the A500.... No automount... nothing...

[pyrre]

Have not updated the indi yet. but all modes, even standard modes get black if i push use.... and i see no highgfx modes in the list from screenmode prefs.

HighGfx is picky about what monitor you use it with. It's really pushing the system to it's limits. Try some of the other modes, like 800x600x16-color SuperPlus, I've found that worked on every monitor and TV I threw at it. At it's most basic, the Indi ECS is just a scan doubler. Do other modes display correctly at 31KHz?  NTSC 640x400, 320x200, etc.?

Also make sure your firmware is on 1.10 (not 1.01) for the more advanced screenmodes. You may need to tinker with the config tool, but the "out of the box" config should work fine with most normal Amiga screenmodes and modern displays.

[pyrre]

And then all of a sudden, the powerled starts to blink and the screen goes green....
damn

EDIT: reseating kickstart seemingly did the trick this time.... Grumpy old gal's these Amiga's

[pyrre]

Maybe the last firmware 1.1 should fix the issue...

==> http://cosmosamiga.free.fr/download/IDEFix_patches.readme


The actual firmware is copyrighted by Jens, good luck with this guy...

Thanks for the heads up.

Seemingly the guys behind elaborate bytes has ceased ALL support of amiga based systems.....

[pyrre]

Oh sorry, I believed Jens purchased the rights...

The enclosed txt file says nothing about rights.
only that some named character at Elaborate no longer works with amiga related projects. and therefor the patch in the "eb_final.lha" is regarded the last and final patch for these systems.
If it is allowed and appropriate i can post the whole txt file here....?

EDIT:
comment on the wiki post regarding this topic:
"Final updates of IDE drivers for iComp products by Elaborate Bytes. This  file was created just before Elaborate Bytes have quit the Amiga  business for good."
Wiki article

[pyrre]

Yes, but the patches Cosmos mentions should be able to fix this. However, the IDEFix_patches.readme file contains these lines though:

Requires:     OS 3.0+ and 68000+
Catweasel and non-flash Buddha users will need to burn the driver to a new EPROM.

Which may be a bit problematic.


Another thing is that just like with the A600 and A1200, standard HDToolbox may need to be patched in order to use CF cards: http://aminet.net/package/disk/misc/HDToolBoxPatch
Or as an alternative, just simply use HDInstTools instead: http://aminet.net/package/disk/misc/hdinst

A noob question, how do i apply the patch to the hdtoolbox i use?

EDIT:
Flashing the buddha did magic for transfer speeds, and querying icons in folder and files in browser panes in dopus goes twice as fast as before.
need to find out how to patch HDToolbox and try CF cards again...

[pyrre]

In addition to the HDToolBoxPatch.lha archive, you will also need this one: http://aminet.net/package/util/misc/gpatch

The below instructions assumes that you are using HDToolBox v40.4

Extract both archives and copy the following files to the Ram disk:

HDToolBox
HDToolBox40.4_MO.gpch
GPatch-2.6

Then enter the following in Shell:

CD Ram:
GPatch-2.6 HDToolBox HDToolBox40.4_MO.gpch HDToolBox-NEW

NB! The old GPatch-2.6 is the only one that works with these .gpch patch files.

I should be able to make that work. though, WB2.1 install comes with HDToolbox V2.22
How much does that matter?

EDIT:
Patches are applied to hdtoolbox. the rom of the buddha has been updated. but the buddha does not show up my cf card, even though the cf card is the only device connected to the controller. i see the leds of the cf adapters blink. but nothing happens. I have even made a special disk for the buddha config. with patched hdtoolbox.

Im starting to go blind...

what else is needed?
do i need idefix in the devs folder?

the strange thing is if i use the buddha_atapi.device tooltype hdtoolbox wont find anything connected to buddha. At all....
but using scsi.device it find hdd's just fine. even lets me partition and boot of one.
And i have used all my knowledge i have ever had in amigas. but im shortcomming....

[pyrre]

My Buddha here is working well with very simple 2.5 CF adapter !


@Pyrre

==> https://www.google.fr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwiew9Wb0aHNAhUsCpoKHbIpAAkQFgggMAA&url=http%3A%2F%2Fwww.doobreynet.co.uk%2Ffiles%2Famiga%2FIDEFix_patches.lha&usg=AFQjCNFxYp8esHgiIVZXae6crqutWF7QEw&sig2=-Gza_jm5znvwnUYtfBFJHw&cad=rja

How did you get your buddha to work?

[pyrre]

In addition to the HDToolBoxPatch.lha archive, you will also need this one: http://aminet.net/package/util/misc/gpatch

The below instructions assumes that you are using HDToolBox v40.4

Extract both archives and copy the following files to the Ram disk:

HDToolBox
HDToolBox40.4_MO.gpch
GPatch-2.6

Then enter the following in Shell:

CD Ram:
GPatch-2.6 HDToolBox HDToolBox40.4_MO.gpch HDToolBox-NEW

NB! The old GPatch-2.6 is the only one that works with these .gpch patch files.

That worked perfectly, thanks

[pyrre]

In reference to #1  I suggest trying a different power supply.  The Indivision ECS is picky about clean power.  On my A500+  I switched from a Obese Boy power supply (not very politically correct name) to a modded XT power supply.  It was like magic the Indivision started working without a problem.  

I got the old Oscope out and looked at the Obese Boy supply, the 5 volt line was a bit noisy particularly when the floppy drive it being accessed.  Before the power supply switch I had all likes of issues with the Indivision.  It would everything from drop signal to have tearing screen issues.

Im using an old EVER AT psu. rated at 230W
Should be sufficient for most amiga use.
and using my multimeter the power of the 5V line seems fine, though i have no scope to test it thoroughly....
At least it drove my A1200 fine for years....

[pyrre]

I will still suggest that you try a patched HDToolBox V40.4 since it's better than V2.22, and yes it actually does work with KS2.0. But you cannot boot the WB3.1 install disk though (fails at the LoadWB command).



I must say that I have never owned a Buddha, but with the IDE controller of an A600 or A1200, the atapi.device is mainly meant to be used with CD-ROMs only. I have a feeling that the same goes for buddha_atapi.device as well.

I have hdtoolbox v40.4 and patched it. worked quite nice. but do not detect any cf cards. it does not detect the IDE-SD adapter either.
However, it is extremely picky about which hdd's are connected.
None of the WD disks works... at all...
and i cant use my "above" 4 gig drives. since SFS require 3.x to work. and the PFS i find only supports partitions of 32mb.

Seems like i am forced to go 3.x if i want to use this computer....

[pyrre]

Wasn't sure if you're still having problems with HighGFX, but in the archive on Aminet there's a file called "OLD_HGFX.GUIDE", and in that guide it says it requires OS 3.x and WB 3.x.  So you might be out of luck if you're trying to use it under 2.x.

FYI, as I mentioned before, I've used it before and it's *very* picky about monitors.  The guide file mentions (quote) "The frequencys are 54 Hz 22 kHz".  Also under ECS it's limited to 4 colors.  My recommendation if you want to use a high resolution mode is to stick to 800x600, which under ECS supports up to 16 colors.  There's several good guides out there on this, including mfilos's:

http://www.mfilos.com/2012/01/a600-trying-800x600-resolution-setting.html

The highgfx has been put aside for a while, must get the buddha working with the cf card. cant stand the noisy hdd anymore....

[pyrre]

@PanterHZ and Oldsmobile_mike

I had been reading on PFS9.5 readme.
So many files, so much to do wrong...

Restrictions and requirements


PFS 9.5 only supports harddisk partitions of up to 32 MB in size.  I
know this is a serious limitation; it will be eliminated as soon as
possible.  It can be installed and automounted in the RidgidBootBlock,
but standard @{"mountlists" Link Mountlist} are also supported.  Memory usage depends on
the size of the partition and the complexity of the directory tree.
It will vary between 70K and 150K.