Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Pete

Pages: 1 ... 6 7 [8] 9 10 ... 58
106
Hardware / Re: Graphics card
« on: 2011.12.25, 05:44:47 »
Hi

@ cyberspittle

Case filters are in place, inside of cases get cleaned every 3 months; no problems cleaning cpu heatsinks only with cleaning graphics card heatsinks.

The main problem is my house is an old building that seems to accumulate dust faster than it is possible to clean...

So, watercooling is an option I'm planning on investigating in the near future.


Regards

Pete

107
Setup & Installation / Re: Can't get printer to work
« on: 2011.12.25, 05:36:01 »
Hi

My guess is that something went wrong during creation of the printer.

Did you use the Desktop -> Local System ->. Printers -> Install Printer to install driver and create the printer?


Regards

Pete

108
Hardware / Re: Graphics card
« on: 2011.12.22, 03:47:56 »
Hi sXwamp

Why would you want to use WarpOverlay anyway? - SNAP overlay (snapwrap.dll supplied with vlc, mplayer, kplayer) works better.

I've been finding the ATI X series cards with active cooling (ie a fan) to be less reliable than those ATI X series cards with passive cooling. I've recently binned 1 * X800, 1 * X700, 1 * X600 as they had all failed due to the fans clogging up (well, not so much the fan as that can be vacuumed reasonably easily but the heatsink vents that the fan blows through cloggs up) causing overheating problems. The X300 with passive cooling (finned heatsink) bought *before* any of the above cards is still going strong though.

I've replaced the above failed cards with X300 cards using passive cooling but with a small case fan positioned to blow across the X300 cooling fins to help dissipate heat.

I guess the best answer is to go for water cooling at some point... or use the computers in a totally dust free environment.

I cannot say I noticed problems with the X series and DOS cmd window; probably because I never install DOS/Win16 support these days as DOSBox covers my simple DOS game playing requirements much better - and has sound.


Regards

Pete

109
Setup & Installation / Re: ECS installation documentation
« on: 2011.12.20, 16:50:37 »
Hi jdeb

What version of Flash did you install? - Flash 5 is a bit outdated and does not work with video that requires a later version; Flash 10 is simply not ready for use especially if SMP is involved.

My workaround for Flash video is

1] Do *not* install the flash plugin for the browser

2] Use a Firefox/Seamonkey extension called FlashBlock to prevent the browser trying to load Flash when displaying a web page.

3] What also comes in handy is software such as ClipGrab to download a copy of Flash video then play it using a choice of modern media players such as vlc, mplayer(smplayer gui), kplayer.

Not sure what you mean by "Snap is o.k. but needs some work apparently". Maybe you can elaborate?

As regards your other points:-

1] Not sure if there is better installation documentation anywhere. If there is it should start with *Always* use the Advanced Install option to have control over what gets installed and where.

I'm sure eCS would not mind if you created better installation documentation and offered it to them.

2] Yes, eCS Support can be slow. I'm not sure how they decide on priorities of problems reported but guess if the problem does not rate high enough it goes to the back of the queue.

3] Update eCS with what exactly? There is the eCS Maintentance Tool that is designed to apply any eCS system updates.

4] Mainly, Yes.

5] I guess that depends on the game/software but there is no obvious reason why not.


Regards

Pete




110
Setup & Installation / Re: Old man needs lots of help
« on: 2011.12.17, 17:27:33 »
Hi marcbryant

For RSJ:-

get rid of the config.sys line BASEDEV=RSJIDECD.FLT - I take it you are using the BASEDEV=DANIATAP.FLT line which makes the RSJ line redundant.
change config.sys line BASEDEV=OS2ASPI.DMD to BASEDEV=OS2ASPI.DMD /ALL - may not be necessary but works here.

You may also find that you have BASEDEV=OS2SCSI.DMD which you probably don't need as you are using the above os2aspi.dmd line.


Not sure what is wrong with your internet connection...

If the setup.tcip is exactly the same as setup.cmd it should work as long as the nic is loading.

To check the nic is loading at boot simply add a "pause" line such as:-

DEVICE=C:\OS2\BOOT\PAUSEIT.SYS

Add the above line just after the nic driver line. When the system discovers the file PAUSEIT.SYS does *NOT* exist it will stop booting and display an error onscreen giving you the chance to check whether the nic loaded - or not.

You could also check the DHCP Monitor in Desktop -> Local System -> System Setup -> Network -> tcpip to see if DHCP is working and check configuration.


Regards

Pete
 



111
Setup & Installation / Re: Old man needs lots of help
« on: 2011.12.17, 03:17:04 »
Hi marcbryant

Problem 1: I suggest you post the contents of the [BootDrive]:\MPTN\BIN\SETUP.CMD file in the hope that someone can spot an error. Is the required nic driver loading at boot?

Problem2: I had Seamonkey failing to start when my internet connection failed recently - seamonkey was not in the Window List but seamonkey.exe was in the Process List. Maybe curing Problem 1 will cure this as well.

Problem 3: Post the RSJ related lines from the config.sys file.

Problem 4: Yes, my guess is that VPC is not finding a connection during initialisation. Curing Problem 1 is probably the answer.

Problem 5: Sorry cannot help with this 1

Problem 6: Several Options available

     a] Try a later driver build from http://svn.netlabs.org/uniaud - go for the Complete Package option to make sure all files are "in synch"

     b] Install the known working build from [eCS1.2 Install CD]:\CID\SERVER\MMECS\DRIVERS\UNIAUD\


Hope the above gives some starting points.

Regards

Pete



112
Networking / Re: Almost dead network after qbittorrent
« on: 2011.12.14, 01:27:35 »
Hi lewhoo

I've not seen this problem at all with qt473/qbittorrent285 - I often have qbittorrent running all the time the system is booted and no problems; currently running while I type this in Seamonkey.

Have you totally cleared out (deleted) *all* files from the earlier build of qt? - If the earlier build was installed using Warpin then it is best uninstalled using Warpin.

Maybe there is a setting that needs tweaking in the qbittorrent Preferences.

Maybe the patched tcpip32.dll is needed for qbittorrent, see http://www.os2world.com/content/view/21034/2/ - I'm using this and guess it could be the difference.


Sorry to leave you with more questions than answers... Hopefully 1 or more of the above will help  :-)

Pete

113
Networking / Re: JetDirect/Port 9100 support
« on: 2011.12.13, 22:46:47 »
Hi madcrow

If the network interface has an ip address and a port name then maybe the SLPR printer port will work  http://kimludvigsen.dk/os2/gfd/sys/prnt/slpr.exe


Regards

Pete

114
Networking / Re: Almost dead network after qbittorrent
« on: 2011.12.13, 22:38:19 »
Hi lewhoo

I've seen that behaviour with earlier builds of qt and qbittorrent but not with the current releases. What versions are you using?

Regards

Pete

115
Networking / Re: ftp passive mode?
« on: 2011.12.12, 19:04:43 »
Hi xchris

Sorry, Looks like I got that wrong - don't use ftp often and when I do it is usually fireftp.

Regards

Pete

116
Networking / Re: ftp passive mode?
« on: 2011.12.12, 01:41:50 »
Hi

ftp clients??:-

FTP-PM in the internet utilities folder.

Want something newer and use either Firefox or Seamonkey? - give fireftp a try; it is an extension for Mozilla browsers. The Firefox version is here http://fireftp.mozdev.org/ Seamonkey version here http://xsidebar.mozdev.org/modifiedmisc.html#fireftp


Regards

Pete

 

117
Article Discussions / Re: SMplayer version 0.6.9 beta 3
« on: 2011.12.11, 03:49:17 »
Hi rudi

The problem is smplayer.ini 0.6.9b3 is crashing when trying to save the mplayer path in Preferences to a new smplayer.ini file and does not work properly with an existing smplayer.ini file that worked fine with smplayer 0.6.9b2.

As smplayer 0.6.9b2 does not have these problems I suspect smplayer 0.6.9b3 is the cause. Note: qt 4.7.3 was/is in use with smplayer 0.6.9b2 without problems despite any changes in the way qt handles ini files.

Regards

Pete



118
Article Discussions / Re: SMplayer version 0.6.9 beta 3
« on: 2011.12.09, 19:27:43 »
Hi David

The only reason I had playback at all - for what it was worth - was the fact that I had an smplayer.ini file with the mplayer path already set.

When I deleted the smplayer.ini file (after making a backup) I found the same problem you have - I can enter the mplayer path in Preferences  but when I click Apply smplayer Exits.

Silvan has not been able to reproduce any of the problems I see with the b3 release. However, I am still waiting for a response to my suggestion that he delete the smplayer.ini file and see if he can then set the path to mplayer without problems. Hopefully he will be able to reproduce that.

Yes, I've "reinstated" the b2 release and have that working fine - which, I think, blows out Silvans theory that because I did *not* install qt4.7.3 using yum/rpm the qt installation/configuration is wrong.


Regards

Pete

119
Article Discussions / Re: SMplayer version 0.6.9 beta 3
« on: 2011.12.08, 19:16:02 »
Hi David

There are certainly some problems with reading/writing smplayer.ini using the 0.6.9b3 release here. Below is the email I've just sent Silvan about this.

If you are having similar problems Please report them to him.

Regards

Pete



The problems I see with smplayer 0.6.9b3 seem to be smplayer.ini related.

I had smplayer 0.6.9b2 installed and working well.

I deleted the files in the \PROGRAMS\MultiMedia\smplayer directory and then unzipped 0.6.9b3 into that directory.

I started smplayer and found Playback very "jerky" compared to the 0.6.9b2 release...

Later attempts to play video files usually (nearly all attempts at playback) resulted in smplayer hanging. It was possible to "close" the gui displayed onscreen from the Window List *but* this did not close smplayer and mplayer; both remained in the Process List and trying to start smplayer resulted in the Window List being displayed. The only way to kill those apps was to reboot.

After trying various tweaks to the smplayer settings and many reboots later due to the failure to resolve the smplayer problem(s) I decided to simply get rid of 0.6.9b3 and reinstate 0.6.9b2 as that had worked well.

So, I deleted the files in the \PROGRAMS\MultiMedia\smplayer directory and then unzipped 0.6.9b2 into that directory.

I then tried playing a video to check that all was working well. It was *not* - seems 0.6.9b2 now has the same problems as 0.6.9b3 ... but how?

Thinking about it the only file both builds have in common - apart from common support libraries (libc, qt) that are working fine with other apps - is the %HOME%\.smplayer\smplayer.ini file.


After the necessary reboot to clear smplayer and mplayer from the Process List I decided to delete the existing smplayer.ini file which is now fairly old having survived various smplayer updates and then started smplayer, which created a new smplayer.ini file, and setup smplayer Preferences.

Every video I tried played well, no problems and no hangs.


I then thought I'd try 0.6.9b3 with this new smplayer.ini file. After deleting the 0.6.9b2 files and unzipping the 0.6.9b3 files in their place I started smplayer and found that playback was working.

Initially playback was very "jerky" and closing smplayer and restarting seems to have got rid of that "jerky" playback. I've now played several videos ranging from 7 minutes through to 95 minutes with no obvious "jerky" playback and no hangs.


The above suggests there is something wrong with smplayer 0.6.9b3 in respect of reading/writing the original smplayer.ini file in use here. Note that 0.6.9b2 only had problems with the original smplayer.ini file that it had been using happily *after* I had tried the 0.6.9b3 release.


However, I seem to have found some problems with smplayer 0.6.9b3:-

1] Clicking the "Stop (Media Stop)" button causes smplayer to Exit - ie smplayer disappears from screen and is not in the Window or Process lists. This is obviously not the correct behaviour for that control, it should simply stop media playback.

2] Volume adjustments do not "stick" - ie I increase the volume, finish playback, close smplayer, restart smplayer and play the same video but the Volume level is the same as when I first played the video, not at the increased volume level.

3] Clicking the Options, Preferences causes smplayer to Exit.


The above could be ini file related.

There could be more problems to be discovered...

120
Setup & Installation / Re: 2.1 install. Help the old man
« on: 2011.12.07, 20:52:56 »
Hi marcbryant

SNAP would be better if it supports your graphics card as you would then be using an accelerated driver.

However, depending on the monitor in use you may find you need to use Panorama during the install but select SNAP as the driver to install.

I say this because a couple of weeks ago I needed to install eCS2.1 to a system using a widescreen monitor. Using SNAP during the install failed as whatever the SNAP resolution is set to for the install produced a "Resolution not supported" message on the monitor.

I got around this by using Panorama during the install but selected SNAP as the driver to install and configure because I knew that I would be able to add the necessary mode to SNAP once the system was booted to a VGA Desktop using the gamode utility supplied with SNAP eg:-
gamode add <xres> <yres> <bits> to add the mode - I used gamode add 1360 768 32
gamode addref <xres> <yres> <refresh> to set the Refresh rate for that mode - I used gamode addref 1360 768 75

Once the mode had been added I selected it on the Screen page of the System object and, after a reboot, it was working fine.

Also, if you have a widescreen monitor then you need to check that the Panorama Widescreen activator supports your graphics card. Panorama does not have widescreen support for the ATI X300 in the system I was installing to whereas, as mentioned above, it is possible to add the required widescreen mode to SNAP for that graphics card.


Regards

Pete










Pages: 1 ... 6 7 [8] 9 10 ... 58