@rwo

I'm currently working on FTDI drivers.
The FT232 serial chip is one of the most popular,
and has been embedded into a LOT of devices.

I signed an NDA and got the documents from FTDI.
I've only been delayed while I finished a hardware
project that I wrapped up two weeks ago.

Yes, I realize that the serial port is getting old,
but I have a lot of serial toys, and I'd like the idea
of having as many as I want off of a USB Hub.

The USB MIDI driver has been quite successful so far,
so I'm working off of that for the FTDI driver.

I hope to get the USB side worked out first, then go
looking for example OS4 device code for that half of it.

It won't be long until I'll be asking for help, I'm sure.



LyleHaze

@nubechecorre

I remember SMUS, CMUS, SONG and MID, but CUST is new to me.
???

LyleHaze

@AmiGame

Just my opinion, but you probably shouldn't keep your cats in the computer case. Kitty litter in the case fan is bad for the bearings. (don't ask how I know that)

Good Luck with the repairs!

LyleHaze

@aldur

It is possible to use regular hard drives on the
smaller HD connector, too.
There's an article showing how to adapt the smaller
44 pin heasder to a regular 40 pin IDE cable.
The writing sucks but the pictures help.

http://www.ncscaug.us/ua1page1.htm

The article also covers serial port and USB hookups,
and other details that have caused problems for some
micro owners.

LyleHaze

I don't recall the year..
I tried to get an A1000 when they were first released, after reading a great article in Byte magazine about it.
But I couldn't get credit, and I didn't have the cash.
So I waited and saved. When they offered $1000 off to trade in your 1000 on a 2000, I went to the local Amiga dealer, gave him $1000, and told him I wanted the best A1000 that he had taken on trade. I also bought Soundscape right there, and picked up "Lattice C" (later Sas) very soon after.

It's been a long time since then, and I'm still involved in MIDI on the Amiga platform. I guess some things just stay.

Through it all, never any regrets.

LyleHaze

@Billsey

If you'd like more information, google the words
"sony rootkit".
Read a bit, and decide for yourself.

LyleHaze

Simple enough, I'm interested in OS4, and so I'll probably
buy whatever it's running on, if I can. I don't much care
what the name of the OS is, and I don't care much what the
hardware is, as long as I can afford one.
PS3 has a lot to offer us. It would appear to have a good
bit of power, and at a lower cost than my micro motherboard. It also has a large manufacturer and a wide distribution network. I expect they will be available for a while. It also has a lot of people out there who might enjoy "discovering" a new OS that's easy and fun to use.
Personally, I haven't bought anything labeled "Sony" since the rootkit scandal, but if that's where OS4 shows up, I'll get over it.
If that's what the future holds, bring it on.

LyleHaze

@LyleHaze

I'm getting a bit forgetful. Must be old age.

Have now added "NallePuh", and I'm getting much
better results.
Not quite working yet, but I'm getting closer..

Thanks to all for the help,
LyleHaze

@Severin

Interesting..
I am using a clean install of final-release, I have made no changes to AHI at all.
The program that I'm wrestling with is DMCS2, which makes major use of the audio channels, but can also be used with CAMD and external synthesizers. I can open it, configure it, and I even got it to play a note once by CAMD, but it gets a LOT of DSI errors related to the audio.device.
I don't believe it ever worked with AHI (but I could be wrong)

I'm no expert at this. I wrote the USB MIDI driver, but I'm not up to speed on the cool tools that are floating around. My classic training never went beyond 3.0

I just thought that SetPatch might give me a wedge that I could use to separate the application from the audio.device. I'm really not sure if it could.

Thanks,
LyleHaze

Where can I learn more about "SetPatch"?
I have read the documents/c/setpatch.doc from the
install CD, and I read devs:NSDPatch.cfg, but I need
more details on exactly how to make it work for me.

I'd like to prevent a classic program from playing
with audio.device. Losing all sound is fine, but it
is giving me fits of DSI's that I'm trying to get past.

Any Suggestions?

Thanks,
LyleHaze

@LyleHaze

Thanks to everybody..
The "Screens" tool is just what I needed.

Now if I can figure out how to keep getting DSI's from
the audio.device, I might get another great classic
application running!

Thanks again, it was finding the documents for it that
I needed.

One of the things that I LOVE about the Amiga community is the willingness of nice people to help out.

LyleHaze

@sundown

I LOVE the avatar.
Looks like family to me!

LyleHaze

@AmigaManiac

Thanks!
I'll try that after work today.

LyleHaze

I remember reading somewhere that OS4 is equipped to "substitute" screen calls from selected programs, to help gain compatibility with classic stuff that might run.

Where can I find more information on this?

When many classic programs open on my Micro-AOne, the screens are often distorted and have large parts unreachable. Should I assume these are fakenative modes that are not configured properly?

I'm tempted to delete all the screenmodes that I don't use regularly, just to try and force programs into using screens that I can actually see.

Any suggestions are welcomed!

Thanks,
LyleHaze

@BobW

Test Post:
If you can read this, something is working better!

Wow, my first successful post on Amigans.net from my
Micro-AOne.
I reduced the mtu and mssdflt as suggested.
I hope this continues to work!!

LyleHaze

[edit] explain the meaning of "Test Post:"

Is there any way to save the current UBOOT settings
to a text file somewhere? This would be a prudent
measure against future battery failure causing the
settings to be lost.

LyleHaze

@Samwel

That was it!!!
I went to AHI prefs, and de-selected the checkbox that
says "screw up the sound while browsing".
Now everything is ok! I'm impressed..

OK, I'm really just having fun, don't take me wrong here.

I've been in a great mood all day, and I got a LOT of good stuff done at work today too.

It's late, but I look forward to getting to the bottom of this in a few days when I get more time. Right now I'll guess that I might still have two soundcards.. the internal and the SoundBlaster.

Hang on.. (digging around behind the computer rack..)
Nope, the SoundBlaster is no longer installed.. But the driver is still in Devs:ahi. I guess I can remove that now..

Rebooting..
Starting TuneNet, the Police, from Zenyatta Mondatta.
Shadows in the Rain..
Starting AWeb.. Yup, still stutters, but not as bad..
Loading a few pages.. the more graphics, the worse it is..
Low GFX pages no longer stutter... But still some breakup on most pages.

It's late.. I'll try some more tomorrow.
So much to do, getting ready for Christmas and all.

Thanks for the help! We will solve this.

Lyle Haze

When you added the heatsink, did you use a bit of thermal grease? It's necessary to conduct the heat from the chip to the heatsink. No need for the "expensive" stuff like Arctic Silver, just the cheap stuff from RadioShack will work fine.

Also, if you want to know which chip(s) are shutting you down, you might want to play a bit with some freon spray, chilling one chip at a time until operation is restored.
Might be a bit hard to get nowadays, it used to be much easier to find before we got holes in the ozone layer.

Finally, check the rotation on the CPU fan.. they work better if they are blowing air onto the heatsink instead of pulling air from it.

Good Luck,
LyleHaze

Well..
version devs:ahi.device returns 6.6
version devs:ahi/cmi8738.audio returns 5.16

I wonder if it might be my USB MIDI driver? It's running,
but traffic is really low. If I shut off both USB MIDI devices
and then reboot the driver won't load.

I also noticed that I still have the older ahi driver for
my soundblaster installed.. I think the card has been
removed.
I'll pull the computer out of the rack and check that tonight
after work.
(I used the SB card for MIDI IN before the usb drivers were completed)

Oh, and the total contents of my WBStartup are:
ScreenBlankerEngine
AmiDock
RAWBInfo
Deficons
ASyncWB
FKey

Nothing looks odd there, but I can remove them all
and try again after work today.

Thanks again for the help. I will dig deeper, but it's time
to go earn a paycheck first.

LyleHaze

Thanks to both for your help..
I have installed the latest CMI drivers, and have
made sure that the task priority is at 20 (it was already there)
I'm still getting a LOT of dropouts (maybe even more than before) whenever AWeb is loading graphics. If the computer
(and AWEB) are idle, the sound quality is great.

I may get a chance to play with it more in a few days. Being
an adult means I don't get as much play time as I'd like

I did NOT load any of the new plugins, but at first glance, I don't think any of them were related to MP3 playback.. But I may be wrong.

Thanks again for the help,
LyleHaze