I've mentioned several problems with OS 4.1 in other topics but wasn't prepared with screenshots and further investigation. I'm running OS 4.1 on a µA1 with no addon hardware; just a stock machine. I still use a dialup connection for Internet access. Here are my main problems:

When Compositing is activated in GUI.prefs with 1024x768x16 screens and IBrowse is opened on it's own screen, grabbing and dragging the scrollbar up and down produces faint lines in the IBrowse window. The MUI versions shown in the 3rd screenshot are not the ones currently installed on my system. I just opened an old file to demonstrate the lines in TurboText. I've also seen these lines in other programs running on the same screen as IBrowse. Here are some screenshots that demonstrate the problem:
Screenshot 1 showing graphics anomaly
Screenshot 2 showing graphics anomaly
Screenshot 3 showing graphics anomaly

I've also encountered some minor graphics corruption with Compositing turned off. The corruption in this screengrab has only occurred 3 times so far. Note the small blue tabs on the far-right and far-left side of the screen:
Screenshot 4 showing graphics anomaly

After being online for more than a few minutes the Dialer window won't close when "Disconnect" is selected. The "shutdown" script is also not executed.

AmiFTP won't upload large files. It stops at about 25k and never continues. In fact, I had to switch back to OS 4.0 to upload the above 150k+ images to my WEB space before I could post the links in this post.

If I boot OS 4.0 with my OS4 boot CD, the Dialer and AmiFTP problems disappear. I also rebooted from my OS 4.1 partition to my OS 4.0 partition (which means that the OS 4.1 Kickstart files are still loaded but the remaining files are loaded from my OS 4.0 partition) and the Dialer/AmiFTP problems disappeared. That leads me to conclude that the Dialer/AmiFTP problems are not rooted in the OS 4.1 Kiskstart files. Because of this I suspected bsdsocket.library. However, when I copied the OS 4.0 bsdsocket.library to OS 4.1 and reset my computer; the Dialer/AmiFTP problem was still present. Therefore I think that the problem is not directly related to the socket library

Can anyone else reproduce any of these problems??

Last edited by Xenic on 24-Sep-2008 at 01:54 AM.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Quote:

After being online for more than a few minutes the Dialer window won't close when "Disconnect" is selected.

ok. That happens under OS4.0 as well.
But since it does NOT close immediately in all cases anyway, you should wait a minute or 2 to see if it does close in your case.

Also, I must say that with several versions of files now and some people transferring newer files from classic to their A1s (yes, we've heard about this in posts), that we should really be listing version #s before discussing this.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6
Quote:

ok. That happens under OS4.0 as well.But since it does NOT close immediately in all cases anyway, you should wait a minute or 2 to see if it does close in your case.

Well, there are times when some transactions are occurring on the connection when it is closed and there is a delay before Dialer closes. However, this is a little more than that. Dialer closes the connection after 20 secs, but the window remains open and basically frozen. It will remain for hours and can be iconified but not closed. With a normal disconnect on OS 4.0 the Dialer window switches to the connect display, closes the connection, plays a shutdown script and closes it's window. I am getting closer to pining down the problem. If I rename OS 4.1 Devs directory and copy my OS 4.0 Devs directory to my OS 4.1 boot partition and reboot, Dialer and AmiFTP work normally. I'm going to replace the files in my temporary Devs directory with the OS 4.1 files until the problem reoccurs. It's going to take a lot of time but I may be able to narrow down the problem to a single file.

I don't know how I'm going to resolve my compositing graphics corruption problem especially if nobody else can confirm it.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Quote:

Well, there are times when some transactions are occurring on the connection when it is closed and there is a delay before Dialer closes. However, this is a little more than that. Dialer closes the connection after 20 secs, but the window remains open and basically frozen. It will remain for hours and can be iconified but not closed. With a normal disconnect on OS 4.0 the Dialer window switches to the connect display, closes the connection, plays a shutdown script and closes it's window.

I've not left the window on screen for hours, but yes...I've seen this window in the exact same condition as you describe. But again, please let me know what versions of files you are using if you isolate this.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6
Quote:

I've not left the window on screen for hours, but yes...I've seen this window in the exact same condition as you describe. But again, please let me know what versions of files you are using if you isolate this.

I have resolved it. I should have known the problem was the a1serial.device because that device hasn't worked properly since OS 4 pre2 or pre3. I should have recognized the symptoms in AmiFTP; uploading large files is impossible. In OS4 pre4 and OS4 Final, I noticed the problem when sending large attachments with YAM. Some of the side effects on the Dialer window seem to be worse with the OS 4.1 serial.device than the OS4 Final a1serial.device but the solution is the same. I have to revert to a1serial.device v51.11 (12/26/2005). Personally, I can't believe they are testing the a1serial.device on the µA1 with a dialup connection or they would have noticed these failures. Try the v51.11 a1serial.device and see if it helps you.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Glad you found the source of the problem. And it's a pity you live in an area where you cannot get high speed. Hopefully that will change soon for you? I haven't used dial-up since 1997 myself...

_________________
AmigaOS 4.x Beta Tester - Classic Amiga enthusiast - http://www.hd-zone.com is my Amiga Blog, check it out!

@Xenic

Quote:

In OS4 pre4 and OS4 Final, I noticed the problem when sending large attachments with YAM.

iirc, you described a freeze and inability to complete "send" in YAM with a large file.
If so, please give me your best idea on a size to test with sending a YAM attachment, and I'll try to reproduce this.

Added:
Is the info in this post (just after July update) still pretty much your issue?
post #91
and...
post #123

#6

Last edited by number6 on 24-Sep-2008 at 03:01 AM.
Last edited by number6 on 24-Sep-2008 at 02:53 AM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Xenic

Out of curiosity, what dialup internet provider do you use? Can you point me to their web page please?

Thanks,

Scott

_________________
AmigaOne uA1-c 512M RAM - Only Amiga Makes It Possible!
Check my blog AmigaOne Computing

@number6
Quote:

Is the info in this post (just after July update) still pretty much your issue?

Yes, but the modem lights don't continue flashing with the new a1serial.device. Other than that the issue is pretty much the same. It's been so long since I reported that issue, that I didn't recognize the symptoms because I first noticed them with AmiFTP this time. Just to be sure, I reinstalled the new serial device and tried sending a YAM message with a large attachment. Yam stopped sending after about 1/3 of the message was sent but timed out more quickly than AmiFTP does and posted an error requester. I ran the test using
the file from the "Screenshot 2" link in my original message. It's a little more than 100k in size.

In addition to the posts you mentioned, I had long discussions on the OS4 ML about this issue. I think that in that discussion it was mentioned that the buffer size or transmission size had been increased to speed up serial communications. My impression of the problem is that the serial device is sending when it should be listening & responding. When I get time I may try playing with the Serial prefs but I don't think those prefs will affect a program that opens the device directly.

_________________
X1000 with 2GB memory & OS4.1FE

@scabit
You can see it in the links I provided for the screengrabs but its D&E Jazzd. It's a regional phone company and I can actually talk to one of their technicians when I call for help.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic
I am having the same problem with FTP. I have had this problem for at least a year that I've noticed. We have been promised highspeed in this area, but it is going to be dish downloads at expensive prices. I will be on low speed 28.8 and less for at least another year or two, so I would like to see this resolved. I don't think I can be of much help technically, but if you need a test run let me know. I have a A1XE G4 OS4.1.
John Paul

@Xenic

As you know from the other threads we have been in together, I also use serial dialup.
I have never seen this freeze after uploading 1/3 of a file with YAM.
I use the latest dev versions of YAM and always update.
My OS4 installation is the public files.

I'd love to help both you and Scabit (who's been in a ton of the serial dialup threads as well), but I don't have many more ideas to offer other than what I've already written to Scabit.

Perhaps MTU? I confirmed mine with my provider, but honestly even before changing it for some experiments, I never had this upload freeze of which you speak.

Puzzling...

@anyone else here using serial dialup

Would you -please- report here if you also have this issue Xenic outlines.

#6

Last edited by number6 on 02-Oct-2008 at 01:06 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6
Quote:

Would you -please- report here if you also have this issue Xenic outlines.

As you have probably already seen, "cope" seems to be experiencing the same problem. As long as I have a working serial device for fall back to I'm not too upset. However, I don't want to buy a SAM/OS 4.1 system if I won't be able to use it for normal Internet activities. As a result I'm waiting for reports from other purchasers before I order a SAM board. I'm assuming that my working serial device would not work on a different board design like SAM, otherwise I could just copy it over to a new system.

I considered MTU but was told that the ISP sets the MTU and that my system should comply with that. That's what used to happen with OS 3.9 with Miami. Speaking of Miami, I was able to check things like the connection MTU with the Miami GUI but don't know how to do that with RoadShow/PPP.

I checked my connection prefs and the MTU is set to 1500. When I look at my Internet prefs, The IP packet type is set to default but I see a ghosted number in the string gadget that is 2048. Is there a way to check my ISP's MTU with RoadShow?

I certainly wouldn't be surprised if this problem has something to do with my ISP but they're not going to change anything that might affect their Windows users. Their idea of technical support consists of walking the user through Windows settings and have never even heard of an Amiga. Probably the only reason I can connect at all is because they have made some changes to accomodate MAC users.

_________________
X1000 with 2GB memory & OS4.1FE

@cope
I can only suggest that you find a1serial.device v51.11 in the OS4 prerelease archives and see if it works for you. It's the only one that works for me.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Quote:

As you have probably already seen, "cope" seems to be experiencing the same problem.

Yes. I'm following this and find it interesting that this is not confined to the Micro A1.

Quote:

I considered MTU but was told that the ISP sets the MTU and that my system should comply with that.

That was certainly not what I've been told. I was instructed to call my ISP, which I did. Once the correct number is entered, then the ISP complied with it, but this is not a case of immediate recognition, as I understand it. Fairly quickly though...

Quote:

That's what used to happen with OS 3.9 with Miami.

I was informed that Miami seeks the MTU from ISP, while Roadshow does not.

Quote:

I checked my connection prefs and the MTU is set to 1500.

Yes, that is the default and as stated above, will not autochange. You need to do that through your connect file.

Quote:

I certainly wouldn't be surprised if this problem has something to do with my ISP

3 of the lesser looked at things when problem solving serial are surely ISP, especially regarding MTU, modem brand/model, and init string. I've also been informed that my former and present modem are much more compatible than others.
Interesting, because I heard this from someone running a BBS for eons and seems to have strong opinions about which modems are best regardless of the OS used.

The longest discussion of serial over a period of over 18 months:
Internet connection under OS4 - still not working
I have bookmarks to MANY others, if you want them.

#6

Last edited by number6 on 02-Oct-2008 at 06:21 PM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6
Quote:

The longest discussion of serial over a period of over 18 months:

I see that I participated in that discussion and actually tried to switch to Miami but never got it working. If I had, I'd probably still be using it. I tried reading the RoadShow docs to set up some port filtering but gave up. Miami was easier to understand and use in my view. As far as things like MTU settings go, one a1serial.device works with my current settings and the other does not. I can only conclude that the difference is in the device and not my settings. I also have another modem (Zoom) and it works fine with the old a1serial.device but not the new one.

_________________
X1000 with 2GB memory & OS4.1FE

I am trying to find a1serial.device v51.11 on the old OS4.0 installs but am having no luck finding them is there another source or does someone know the specific update it is found on?
Thanks,
John Paul

*I just found it. I will try it next reboot.*

Last edited by cope on 03-Oct-2008 at 09:42 PM.

@Xenic

Quote:

I also have another modem (Zoom) and it works fine with the old a1serial.device but not the new one.

ok. You know my former modem from the old thread.
Current one working is a SupraFax 28.8.

What I'd really like here is for anyone else using serial dialup to post here in order to have a crack at diagnosing this.
Am I the only one with working a1serial dialup with current files? (non-beta)

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6
Quote:

Am I the only one with working a1serial dialup with current files? (non-beta)

I hope not! Both of my modems are 56k so maybe the slightly older protocols work more reliably. Both of my modems are set to negotiate the optimum speed (and protocol?) and maybe that speed is too high for large file transfers. I usually get connection speeds of 28,800 or 31,200. What is your normal connection speed and MTU setting?

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

Just to review:
My former modem was Best Data Smart One 33.6 Kbps Plug & Play Modem.
No issues whatsoever and I was informed this modem was one of the most reliable, when discussing this with the BBS fellow.

My current modem is SupraFaxModem 28.8. Again, no issues and highly recommended.

Also, all the reports I've read here about issues seem to revolve around the 56k modems, yes.

The final entry added to my connection file is:
mtu=576
As stated previously, I called my ISP to confirm this was still valid for the dialup part of their services offered.

Line 3 in my connection file:
speed=28800

Actual speed, remembering that the new a1serial.device HAS been optimized and performs a LOT better, is about 2600 cps. (about 1700 cps prior to this)
2600x8=20800, right?
That would be actual speed less than speed entered in connect file. I can not say if that is relevant, but possibly...

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*