Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
100 user(s) are online (72 user(s) are browsing Forums)

Members: 0
Guests: 100

more...

Headlines

Forum Index


Board index » All Posts (xenic)




Re: OWB 3.13
Just can't stay away
Just can't stay away


@joerg
What happened to the network progress bar that previously appeared in the lower right hand corner of the OWB window?

When I clicked the link to send this message, this page loaded with the last part of the link still visible at the lower right where the progress bar used to be. When I moved the pointer over another link, the old link residue disappeared. It's kind of a nitpick just to report it. It's no big deal really.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@daveyw
Quote:
I am really confused with regards to the a1serial.device. Some people seem to be saying, use the older version. Others say use the new version. I am using 52.1, which is also confusing, as I was under the impression that I had OS 4.0 final? (Workbench is 52.1, Kickstart is 52.8).

I just checked my backup of OS4 Final and the a1serial.device that came with it is v52.1. On OS 4.1 I have v52.4 but both of those versions fail when I try to send a large file with YAM or FTP. Since you now have a 56k modem working on your system, try sending a message (to yourself if necessary) with a 100k+ attachment. I would be really surprised if it works for you. On the other hand the problems that some of us encounter may only be with ?A1 and not an A1.

I noticed problems with iconified Dialer back in OS4 prereleases and have never iconified it since. If left uniconified, it seems fairly stable with the right serial device. As far as reconnecting after a reboot, that worked in the earlier OS4 prereleases by adding the setting "nullmodem=yes" to a copy of your configuration file that you could use after a reboot. I think it stopped working in OS4 Final but it could have been earlier.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@number6
Quote:

Hmm...Miami V2.1p (registered) worked straight away for me with every OS4 update I tested it with. So...there is still something different about your setup imo, or it should have always worked for you as well.

No. I think it was my stupidity. I just checked my OS4 prerelease backups and I did not have "C:AddNetInterface" commented out in the prereleases. I don't think Miami works if the Roadshow "bsdsocket" library is already in memory. Once I got the Roadshow Dialer working well, I never tried Miami again (if fact I deleted it but have it on a backup disk). I now have the "C:AddNetInterface" commented out and Miami works.

I downloaded the OS3 version of YAM and replaced my OS4 binary with the OS3 version. The OS3 version of YAM 2.5 seems to work fine with Miami. I reinstalled the newer version of a1serial.device (v52.4) and tried sending a message with a large attachment. The result was essentially the same as with Roadshow Dialer; YAM stopped after the first 24 bytes sent and then timed out. It seemed to stop even sooner with Miami than with Roadshow.

There is a new SAMep user on the OS4 ML who is also using dialup and has similar problems. His problems seem even worse than mine when he uses one of his 56k modems but his 28.8 modem is working for him. I think he is having some problems with the Dialer GUI acting up but I need to find out if that is only with the 56k modems or with the 28.8 also.

The above info seems to confirm that there is a serial/modem problem when using 56k modems. Since I don't have a 28.8 modem, I'm getting a little worried about my SAM Flex order. I'm not sure if I should cancel it until this issue is worked out or just take a chance.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@number6
I decided to start my old Registered Miami (not DX) to check the settings I used with it. To my surprise, it actually connected when I accidently selected the "Online" button in the main window! I could never get Miami to work with prerelease OS4 and had given up on it. Unfortunately, YAM won't work with it so I can test the newer OS4 serial device with YAM and Miami. What I've discovered so far, is that programs that open bsdsocket.library with a minimum version of "0" seem to work and those that request a higher version (2, 3 etc.) don't. IBrowse, Jabberwocky & AmiFTP work while OWB & YAM don't.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@number6

Quote:

number6 wrote:
Thank you for continuing to assist on the testing. It's pretty much down to you and me now. Frankly, it may be helpful to continue to have you test on SAM, whilst I compare vs the Micro.
#6


I tried commenting out the "INTERRUPT=Yes" tooltype in the Radeon monitor driver and sending a message with a 1MB attachment using YAM and v52.4 a1serial.device. The result was the same as before. YAM sends about 40-50KB of the message at a very high rate and then stops. Eventually YAM times out and throws up an error message. At that point my Internet connection ceases to function. The modem connection light is still lit but nothing works. IBrowse can't get a response from DNS servers, Jabberwocky can't connect and the Dialer GUI is frozen.

With the newer serial device, YAM shows message uploading in 5-6KB increments very rapidly until it stalls. With the older serial device YAM shows message uploading in 1-2KB increments at a slightly slower rate. With the old serial device YAM shows download speeds of 3.2KB/s and upload speeds of 2.4KB/s. I'll have to try the new device again to see if I can get it running long enough to give me a speed reading in YAM.

Do you know if the ?A1 a1serial.device will work on a SAM? I would assume that the port addresses would at least be different which would mean it probably won't work. If all else fails, I can PM you for an address and send you one of my modems. I'd like to get the SAM before I proceed though.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@number6
Unfortunately, I didn't seem to get my SAM order in soon enough so I'm still waiting. In the mean time, I noticed a new SAM Flex user on the OS4 ML who doesn't seem to have a positive impression of the Roadshow dialer. He is also a dialup user and I am going to ask him for some details. A number of people who previously used Miami on a classic Amiga don't seem as happy with Roadshow. I felt the same way when I first switched to OS4/?A1.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@daveyw
Personally, I don't think your problem is really a Roadshow problem but actually a modem/serial problem. Please let us know if any of the suggested solutions solve your problem or if you have found a solution of your own.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@number6
Quote:

number6 wrote:
Surely there must be people with old unused modems that match one of mine that I constantly write about.

Best Data Smart One 33.6 Plug&play
SupraFaxModem 14,000/28,800

If someone could send you one these...my offer still stands.

In that case I would send you all of my settings that DO work and we can settle this once and for all.

From what I have seen, most of the people experiencing these problems are using more up-to-date 56k modems. I purchased a "Zoom" modem about 6 months ago and it has the same problems if I use the newer a1serial.device. It would make more sense to me if the a1serial.device programmer tested the device with a (one or more) 56k modem and fixed it to work with curently available modems. I know you're happy with the optimizations that increased the throughput with your modem but I don't think dialup users should be forced to hunt for old modems in order to get online. The current solution for people experiencing this problem seems to be to try one of the modems you suggest or revert to an older a1serial.device.

Since one of the IDE busses on my ?A1 has failed, I've ordered a SAM Flex system. Therefore, I'm not that concerned about the serial issues with my ?A1 because the older serial device works well. However, the first thing I will do when I get my SAM is to connect to the Internet to be sure it works properly with a 56k modem. If not, I'll report it in Amiga forums and return it immediately.

More on topic; I think this thread should be "modem/serial problems" since I don't think this is a RoadShow TCP/IP problem at all. Hopefully, the original poster has gotten enough hints to get his Internet connection working.

Go to top


Re: Soooo many problems with Roadshow
Just can't stay away
Just can't stay away


@Hans
Reverting to a1serial.device version 51.11 solves dialup modem problems for most ?A1 users. I think it's the version that came with OS4pre4 but I'm not sure. Every time a new version has been relesed since then (OS4 Final, OS4.1 etc.) I have tried the new version but had to revert to the older v 51.11 for my dialup modem. Most notable symptom of newer version shortcomings is the inability to complete large uploads or send messages with large attachments.
I've complained about this on various forums and in the OS4 mailing list every time a new version of OS4.x is released but nothing gets done.

Go to top


Re: Serial and dial up
Just can't stay away
Just can't stay away


@BillE
Maybe we could email you if there actually was an email address in your profile . Strangely, the forum lists you as being online right now. Edit: Oops, no it doesn't.

Go to top


Re: OWB 3.11
Just can't stay away
Just can't stay away


@ChrisH
Quote:

ChrisH wrote:
@joerg
It looks like you have to register, just to submit a bug report! I'm afraid that I am sick of having to register for everything (different password for each damn one), and I suspect other people will find it a disincentive too.


You know, that's really sad. Joerg is working his ass off to give you a free browser that is the biggest improvement in WEB browsing we've seen on the Amiga in a couple of years and you won't even take the time to enter a couple of words on a WEB page. Sure, go ahead and wait for the rest of us to help Joerg debug the program and then we'll hand it to you on a silver platter.

Go to top


Re: OWB 3.10
Just can't stay away
Just can't stay away


@Slayer
I like OWB but I must say that v3.10 is unusable for any extended period of time.
I can understand an expanding memory cache as more sites are visited but the current memory usage goes way beyond what would be reasonable for additional caching. I just visited AW.net after a cold boot. I clicked a single forum link, waited for it to load, clicked the back gadget to return to the main page, waited until it loaded and repeated that process over again more than 20 times. Each time I went from page to page (the same 2 pages over and over) I lost about 5 MB of memory. Occasionally I would lose 20+ MB. Both pages should either be cached or getting reloaded, but I shouldn't be losing memory simply by switching between the same 2 pages multiple times.

Typing this message just took me from 200MB to 8MB free memory. I had to quit OWB and start it again because my system was slowing down. Almost all the memory was returned when I quit OWB and the several MB that was not returned could be accounted for by opened libraries/devices etc. I'm afraid I'll need to revert to an earlier version of OWB like some other users. The memory consumption with this version (v3.10) is just too outrageous.

I using a ?A1 with OS 4.1.

Go to top


Re: OWB 3.10
Just can't stay away
Just can't stay away


@broadblues
I just viewed the source for this forum page and it seemed normal. Blue horizontal lines have been an intermittent problem for my ?A1 since OS4 Final. I get lots of them in random windows with compositing turned on. I can only suggest trying the source view with compositing off.

Go to top


Re: OWB 3.8
Just can't stay away
Just can't stay away


I tried OWB 3.8 for most of the day yeaterday.
The good news:
1. I am now able to access my bank account.
2. I can download files directly.

The bad news:
1. OWB crashed when clicking the back arrow button to return to a previously visited URL. Crashlog submitted at OS4Depot this morning.
2. OWB freezes my system while entering text. I was unable to submit my crash log with OWB because it froze the system each time I tried.
3. OWB did seem to be using up memory but I was unable to use OWB long enough to use a substantial amount of memory. From my perspective the memory usage could have just been and expanding memory cache.

Does the OWB memory cache grow as more sites are visited and is there a max amount of memory it will use? It might be useful to have a TOOLTYPE to set the max cache size.

Go to top


Re: OWB 3.8
Just can't stay away
Just can't stay away


@Raziel
Quote:
Plus it looses all cookies, because it doesn't seem to write to the cookie file i gave it in Tooltypes COOKIEDB=Cache:OWB/CookieDB
I have to log in everytime i visit, last access to CookieDB was yesterday O_o

Cookies are working here. Maybe it's the way you named it. In my OWB TOOLTYPES it looks like:

COOKIEDB=Back:owbData/cookieCollection.db

There was no file when I started and a cookieCollection.db file about 6k long when I quit.

Go to top


Re: Made with Amiga campain
Just can't stay away
Just can't stay away


@AmigaBlitter
Quote:
I used Poser and some Photoshop stuff.

Don't you find it a little ironic that you have to use another operating system & software to create a "Made with Amiga" logo?? I can't even edit or create the new "System" icons for OS4. I'd like to see every part of OS4 produced on an OS4 Amiga before we start bragging about "Made with Amiga". How much of the OS4 docs, PDFs, images, icons, programs, etc. are created/compiled on an OS4 Amiga?

You've made a great logo though. Let us know when it's completely made with Amiga

Go to top


Re: OWB 3.7
Just can't stay away
Just can't stay away


@ktadd
Quote:
ClipDown doesn't support JS links either. How do you find the file link from a JS link?

Probably by having a JS interpreter and maybe even access to the Browser's Cookies for the site or page. I doubt if any stand-alone D/L programs will succeed for JS links. I think one of the reasons for JS links is to prevent direct file access from Google (or other search engines). The Hyperion site, for example, wouldn't want direct links to files that you must be a registered user to access.

Go to top


Re: OWB 3.7
Just can't stay away
Just can't stay away


@Menthos
Quote:

Well, sure it works but is way to "complicated"...

Yes, it is more complicated but Amiga users have always had to be more imaginative and capable in order to accomplish some things that are built into mainstream operating systems. Programs like IBrowse, TurboText etc. allow the user to define ToolBar & Menu commands and accomplish things that are not even possible with other systems.

It certainly wouldn't hurt to have one or two user definable (through TOOLTYPES) spots in the OWB popup menu. However, since there are so many ways to get D/L with other browsers or external programs, I think we should let Joerg focus on more important issues for the time being. My Amiga is my only computer and things like accessing bank accounts and essential WEB sites is far more important to me than having builtin D/L. Before OWB was released, I was shopping at the local MAC store and looking at a replacement for my ?A1/OS4 computer system. I only want one computer on my small desktop and not a network of computers that will fill and entire room. I need to be able to log into my employers WEB site to perform personnel actions, my bank & credit union WEB sites for account control & government WEB sites for doing my taxes etc. OWB has cured most of my Internet problems and my computer replacement is now on hold.

We don't "NEED" OWB for D/L at this point. Let Joerg focus on compatibility issues for now.

Go to top


Re: OWB 3.7
Just can't stay away
Just can't stay away


@Menthos
Quote:
Menthos wrote:
About downloads: would it be possible to just add a configurable context menu item that can call a command with the url or is that a too ugly hack to implement too?

If you check my other posts, you'll see that I have implemented something similar (as a hack) but there are problems which I discovered when D/L the quick updates from Hyperion. JavaScript links don't seem to work with the external commands I have tried. I think a JS link requires some sort of JS response that some external D/L programs can't handle. I'm going to investigate ClickDown to see how it handles JS downloads.

Go to top


Re: OWB 3.7
Just can't stay away
Just can't stay away


@COBRA
Quote:
COBRA wrote:
While I agree that it should be done properly, in the meantime it would sure make it easier to add a simple 'Save Target As' option in the context menu which would bring up an ASL requester for saving. It would be nicer than having to load all the binary data into the page as garbage, every time somebody wants to save data.

Actually, IBrowse opens a browser window before it opens the D/L requester. It just doesn't fill the browser window with garbage most of the time. If you try to D/L a file that has a text MIME instead of a binary MIME even though it's a binary file, IBrowse will fill the browser window with garbage instead opening the D/L requester.

Maybe Joerg could add a "nodisplay" command for window opening so that the D/L browser window would not fill with garbage. It would still be a temporary solution until a proper D/L can be implemented. Since AWeb is opensource, maybe Joerg could borrow some AWeb code for D/L. In fact, I've wondered if it would be possible to use OWB as the display engine for AWeb.

Go to top



TopTop
« 1 ... 60 61 62 (63) 64 65 66 67 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project