• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu
Menu

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.

Show posts Menu

Messages - StefanZ

#1
Hello Roderick,

thank you for your reply.

The main idea behind my question was if there is anything specific what I can do - as a single end user - to make sure that my system is better support in the future versions of ACPI?
...or is it better to wait for newer versions of ACPI that will get progressively better?

(I decided to act because it seems a bit ridiculous why my (standard Intel) system should not be supported at any time by any  of (even  the old) versions of acpi. I'm getting worried a bit that my system might actually never be fully supported...).

Thanks.
St.
#2
What should one do, if running on Intel ICH9 family chipset and gets this out of ACPI:

This system does not support CPU Performance Control via ACPI.

This system does not support CPU Throttling.

Thermal information:
 No Thermal information is available for this computer


Does it mean my system is so nonstandard?  :'(
St.
#3
Utilities / Burning CD/DVD on AHCI system?
2012.09.05, 14:19:43
Hello everyone,

is there a way of burning the CD/DVD media on AHCI system?

So far it seems that every burning solution needs some kind of SCSI support/masquerading, which does not seem to be working/possible on AHCI system.

St.
#4
Agreed.

...and there is one more thing:
majority of today's MSDs are being used on Win* systems. This means that majority of these MSDs are not unplugged safely and are in "dirty" mode. eCS will have to either have a way of how to check the filesystems for all possible issues or have the possibility (as win does) to ignore this dirty flags.

Because again, without this we will all these devices just for read-only, nothing more.
#5
Wow!

Power-off works now!!!  :D
#6
Quote from: RobertM on 2012.05.24, 02:08:44
Actually, this is not solely an eCS issue. This issue exists and persists in the Windows world as well. There are countless posts from people who have bought new SD cards for their phones, formatted them on a Windows machine, and watched (a) them be unusable on their phone or (b) experienced data loss or data corruption on their phones.

Now... for those who have formatted their cards on their phones, then inserted them into their Windows machine, they've noticed a variety of interesting issues as well. In my case, all sorts of corrupted files when I performed a simple copy. The only way that worked for me was to plug in my entire phone, copy off the card to the Windows machine, install the new card in my phone, format the new card in my phone using the phone's format utilities, and then copy to/through the phone to the SD card (ie: again, I could not copy directly to the card without causing corrupted data - or a situation where Windows "fixed" the card in a fashion where the phone now saw data corruption or could no longer use the card).

In all such cases, the only guaranteed method (and the only method approved by many of the phone manufacturers) is to format the storage device in the device using it (in my example's case, the cell phone), connect the *entire* device to the computer via USB and do all transfers that way. Anything else risks (or nearly guarantees) data loss, data corruption or storage media that is no longer readable by the device (ie: cell phone, media player, etc).

The other issues? Yeah, the USB and MSD stuff does still need some work - but that's not related to this particular issue.

Hello Robert,

as long as I agree to your statement about file system operations being messy on these devices, as well as I agree to the fact that even Win/Linux might not have 100% success rates of USB MSD usability, I still have to insist on the validity of my comment:
The point here is not that even Win/Linux are not perfect in this sense, the point here is that all the other OSes are LIGHT YEARS ahead in success rates of this USB mass storage useability.

Unfortunately we have to face the harsh truth here: eCS's capabilities in this field are currently EXTREMELY limited, and this limitation will stick to the system and to the users unless somebody takes the stand, updates the code and brings it to the working level of at least Linux, if not win systems.

Honest - it is getting quite annoying to i.e. buy a USB stick and not know if it will work with eCS or not (my success rates are currently below 50%, with a bit more specifi devices - smartphones, mp3 players, book ereaders, USB printer - the success rate with eCS is close to 0%!!!)  >:(

St.
#7
There is more problems.

The biggest is the one where the device expects certain FAT32 format with certain geometry and boot code.
It happens (very often) that this device is not readable by eCS, even DFSee will report i.e. geometry error.

If you "fix" it using DFSee and eCS is able to mount the drive, then it usually happens that due to changes the device itself is not able to mount (or see) the drive. I had this experience with Amazon Kindle 4.

So in my opinion the LVM + USB + FAT32 in eCS needs complete overhaul to see/mount even "strange" FAT32 formats on various external MSDs. Until then, eCS will never be fully usable for USB mass storages.

St.

#8
Applications / Re: odin 0.8.3
2012.02.23, 22:53:09
Hmmm, interesting.

No matter what I do, each time I'm trying to run something under Odin I get this error:

Can't load/find kernel32.dll (rc=2, module STDCPP)  :(
#9
Hardware / Re: LVM-less USB MSDs?
2011.12.30, 10:51:29
Quote from: RobertM on 2011.12.29, 21:44:28
Not the answer to the specific question - but FTP is your friend. In your scenario (if I am understanding it properly) one would use Peter Moylan's FTPd on the OS/2 machine (and yes, it supports JFS files greater than 2GB) and some FTP client on the Linux (or Windows, or OSX, etc) machine. Works for me all the time.

Hello RobertM,

I have to admit, I never thought of this possibility. I was rather focused on getting access to the the local (&external, i.e. USB) hard drives and filesystems. Thanks a lot for a good pointer  :)
#10
Hardware / Re: LVM-less USB MSDs?
2011.12.26, 16:47:29
Quote from: Joop on 2011.12.26, 14:27:35
Ah, nag nag nag and so on. This is an OS/2 - eCS forum, so you don't see the problems with Windows or OS-X. I do have both and they have their own problems. Windows most due to illegal actions on the stick, or never asked yourself what that small file has to do on your stick? Also OS-X seems not free of trouble if it comes to USB media. As far as I know Linux has also a mount and demount thingy, so what's the point to nag OS/2 for its mount and demount procedure?

Hello Joop,

no no, it is not just nag nag nag :D, and yes, you are correct, this is eCS forum, so my intention was to rant a little about eCS related issue.

For the USB mount stuff, unfortunately my experience (for the past 2 years) tells otherwise. In other OSes you are usually able to plug the thing into PC and in 99% it gets mounted - without crazy errors, without OS ranting about something not being possible. Does not matter if this is USB thumb drive, e-book reader or your smartphone. It just works (and yes, in Linux too). In eCS, you get lucky if the thing works at the first try. Usually it does not and then you have to put forth a reasonable technical effort to make it work (also quite often without a certainty of success).

All of this gets specifically visible if I want i.e. my mom to use eCS. It is very hard to keep explaining why something cannot be done :(

It is - of course - not only this one thing that gets my blood pressure high for the last months. There are more, much more things that I'm getting tired about.

And I decided to rant here a bit :) because I have a feeling that maybe we, as end users, do not get enough attention for the last years from the keepers and maintainers of eCS. I'm working as project manager in a global-business corporation and of course I understand that end users might not be a priority (definitely not on a long term run) for doing big business for SSI and Mensys. Also, eCS has lots of more important things to be done and improved upon, so available resources are spent elsewhere. I understand that. But for the last months I'm feeling like I need a break from constant fixing, beta testing and waiting for new drivers, fixes, functionalities etc.

I do not mean it in a bad way, just thought that the community might get interested in discussing the thought too.  ;)
St.
#11
Hardware / Re: LVM-less USB MSDs?
2011.12.25, 13:41:00
Quote from: cyber on 2011.12.25, 02:18:47
Good luck and welcome to light side of the Force. ;))))

Well, if you saw how I'm sometimes hacking eCS, that is what I call geeky..
For the various support of various filesystems, the biggest issue is with devices where you cannot do whatever you want. I.e. now I bought new Amazon Kindle 4 for my mom, but guess what, eCS is not able to read FAT32 used by the device (and believe me, it is not by the lack of me trying...).

Nevertheless, despite being quite frustrated by lack of development of basic things on eCS (for the past 10 years or so), I still love the OS and consider it being a light side of the force :D.

By migrating to *tux I would consider myself becoming a kind of "grey" version of my previous self ;)
...I guess it is not necessary to state which side of the force is the dark one (actually, it is the The One Whose Name Cannot Be Spoken ;)).

St.
#12
Hardware / Re: LVM-less USB MSDs?
2011.12.25, 01:58:15
Quote from: cyber on 2011.12.25, 01:50:06
One of main reasons I migrate.  Look at this from brighter side, noone can steal data from Your OS/2 computer on to flash stick like in movies always do, with those stupid other OSes.  :D

Weeeell, I have actually already migrated, just by a coincidence, the latest incarnation of Linux Mint (v12) is kind of getting "unusable" the same way the Ubuntu does :D and that slowed my migration down a bit (also when combined with not having enough time due to business trips and lots of work otherwise).
...and I was too lazy to figure out a way on how to access and migrate all the data from os2 jfs to something *tux like...
Nevertheless, I know what you are talking about, I'm already down that road too...

Still, not the answer what I hoped for :(
St.
#13
Hardware / LVM-less USB MSDs?
2011.12.24, 23:02:03
Hello everyone,

for the last couple of year I'm steadily getting upset about USB devices.

It is quite usual that majority - if not all - USB MSD devices are normally readable in all the other OSes. This includes devices such as new USB thumb drives, external USB disks, Amazon Kindle etc.
It seems that eCS has still MAJOR issues with working with these devices, where 99% of these are not readily usable with the system (without any high-tech changed via LVM or DFSee), and approx 50% of these seem never to be able to work with eCS, no matter what you try. One of the main issues here seems to be extremely picky eCS disk "subsystems", which work in a way that if any non-standard setup is detected on USB device (today this covers 100% of the devices available!) the eCS just refuses to work with the device...  :'(

Does anybody have similar years of painful experiences? What about the possibility of having LVM-less USB MSDs (at last)?!  :'(
#14
Storage / Re: Help: Recovering a volume
2011.10.22, 00:57:28
Just a sidenote:

I had similar results caused by different issue source: I tried to install new Ubuntu, which did something daemonic with my extended JFS partition (350GB E:). As a result, this E: volume was not accessible, although in DFSee it was visible as "-e" and seemed to be in order. eCS just refused to access it.

One - although rather drastic - trick helped, proposed by Jan van Wijk (DFSee developer): manual change of partition type from original 0x35 (LVM) type to standard IFS Bootable JFS eCS type 07. This helped and suddenly the partition started to be readable again, in fact, I'm using it successfully until now.

The point being that "something" in Ubuntu (later versions of GRUB?) touched without my knowledge the extended JFS partition and changed "something" in there. The result of this partition type change solution was that eComstation started to use bootable version of JFS drivers to init & access the partition in question.

Nevertheless, the cause in your case seems to be quite different, so the question is if this is really worth a try  ???

St.
#15
Article Discussions / Re: Qt version 4.7.3
2011.09.24, 20:28:46
xsystray.dll is not part of the compiled release?  :-[