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 - Doug Bissett

Pages: 1 ... 90 91 [92] 93 94 ... 97
1366
General Discussion / Re: Hobbes directory structure re-organization
« on: May 31, 2013, 04:54:27 am »
Hi.

I'm proposing a file structure reorganization at hobbes. I will like to have some discussion on the forum of what can be improved on the hobbes directory structure to store files.

I currently made a draft on Freemind about the structure based on the current one that hobbes use. I'm sharing this files for you to comment.  Fell free to modify it and present any option, or give any comments.

Regards
Martín

I doubt if your effort will be rewarded. You must remember that HOBBES is managed by a student, who is learning how to do such things. They rarely have enough time to manage what exists, never mind try changing it in more than the most minor ways. It appears that nobody else does much, if anything, with HOBBES, and a student isn't likely to learn enough, in 4 months, to be able to make large changes, without major disruptions. Plus, they need time to go to classes.

Then, there is the problem where there are thousands of posts, all over the internet, that link to files where they exist today. Changing HOBBES would likely break a lot of those links.

FWIW, I think that HOBBES is not well organized, but most of the problem is caused by those who upload things to inappropriate places. Reorganizing things, isn't going to fix that problem. It is, after all, a user operated service, with a little help from somebody at NMSU. It is usually pretty easy to do a search to find what you are looking for (as long as it has been properly described by the uploader), so there doesn't seem to be a pressing need for changes to HOBBES itself. However, if you want to encourage users to make more logical decisions about where to put things, and how to properly package (and describe) what they upload, the problem may be fixed, eventually. The other thing that could help, is to document all of the obsolete software that is at HOBBES, and see about getting rid of some of the overhead. Of course, as soon as something is removed, somebody will be looking for it.

Overall, I am very impressed with the way that HOBBES works, today. It is certainly not perfect, but it is better than most file repositories.

1367
Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: May 29, 2013, 06:15:11 am »
Hi Doug,

You are probably correct about the one in a hundred, but it's extremely frustrating.  Take libusb for example. I'd estimate I spent 20 - 30 hours working on it, possibly more, over a period of several weeks. Now that the port is available, it opens several doors in terms of other software that can be ported & used on OS/2.

I think that something like libusb would mean something only to other developers, who might need it for a project that they are working on. A normal user would have no need for such a thing, by itself. Since you asked for help, those who try to do more than sit back and wait, stepped forward, and did some testing. I must admit that I, for one, did not see any use for it, until you mentioned USB scanners. Whether it will actually turn into something useful, or not, remains to be seen, although initial reports from those who did some USB scanner testing, would seem to be somewhat encouraging. Then, there is the question about how many OS2/eCS users even have a USB scanner. I would bet that there are not a lot. If libusb turns out to be useful for scanners, there may be more, in the future. I for one have an antique Epson ES-1000C SCSI scanner, that doesn't want to work on recent hardware, and SCSI is becoming more of a problem, so I am thinking about getting a new scanner. I expect that it will be USB, when I find something that will likely work. Unfortunately, you usually cannot buy something, and return it just because it won't work with eCS.

I don't *personally* need any of these ports. My desktop OS has been Ubuntu since April 2011. The work I do on OS/2 is purely for a) entertainment and b) because I still have a soft spot for OS/2. I get a lot of satisfaction from getting things working, but in some cases, I put things out there via places like os2world, and based on no feedback - so I don't even know if they're found to be a) useful of b) work they never end up on my site as I don't want to link to things that a) aren't useful or b) don't work, to the possible detriment of other users.

We all appreciate what you do, many just don't bother to say so.

Perhaps you need to split your web site into two parts. 1) with "proven" software, and 2) with "experimental" software. When somebody reports that "experimental" software works, move it to the "proven" area (perhaps three good reports would be better). In fact, three parts, with the third being software support stuff, might make sense.

As for "aren't useful": I admit that I find a lot of what gets ported to be "not useful". I hate to say so, because others obviously find some of it to be useful, and every once in a while, I go looking for something that has been around for a while, that I didn't find useful when it first appeared. Perhaps you need some way for users to request "useful" ports. That would, of course, lead to porting libraries etc. Just picking something, because it sounds like something that people would like, will work sometimes, but spending two weeks on a picture viewer is probably a waste of time, because we already have PMView, which is hard to beat.

At the moment, I have been putting off collecting the information required to try to get Uniaud to work on my new Lenovo ThinkPad L530 system. Version 2.02.01, produced by DAZAR1, creates sound, but it is not right. Older versions won't even load. Now that David A. has got the Realtek Multimac driver working with it, I should get on with reporting the Uniaud problem, but I must admit that sound, on a laptop, is not a high priority for me.

If you are looking for something to do (yeah, right), Have a look at http://www.thinkwiki.org/wiki/Thinkpad-acpi. There is some indication that the program might enable WiFi radios on ThinkPad models where GENMAC/XWLAN won't do it. It has a number of other "interesting" features as well.

1368
Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: May 28, 2013, 06:44:57 pm »
I should also add that based on the amount of feedback on hplip and other things in general, I don't know that it's worth the significant effort that would be involved in getting PyQt and the hplip python scripts working.....

Hi Paul. Please remember that only about one in a hundred will say anything. Most users are not even sure what you are talking about, but they do appreciate the work that you do.

Personally, I have been using CUPS with my Canon i960, but it doesn't work properly. There seems to be something messed up in the configuration, and it cuts off about 5 mm on the right side of the page. The old OMNI driver, for the Canon i950 works better (and a LOT faster). CUPS does print though.

My brother has a Canon MP620, that you got working about a year ago, using WiFi (bjnp.exe, which doesn't seem to exist in the latest CUPS packages). At the end of June, I will be trying to update that again. Hopefully, the update will be done by installing eCS 2.2 GA.   :)   I will also try to get the built in scanner to work, if I have the time.

Meanwhile, I have been looking at what is available to update my own printer. The i960 has been showing its age, recently. It seems that every printer on the "working" list is not available, and there are newer ones that have replaced them (compatibility unknown). I probably won't get serious about that until August, but it seems to be a real problem. New printers, that are supported, don't even exist on the clearance shelves (but I haven't spent a lot of time looking, yet). I suppose that one answer would be to get an Apple printer, which is likely to get support, eventually. I am considering getting a color laser printer, but I don't want to spend a lot of money on something that I don't use very often.

About 30 years ago, I attended a presentation by IBM, where it was stated that printers probably wouldn't exist by1990. I knew that wasn't going to work when I saw the presenter check his e-mail, and print every one of them so he could read them (shredding them after reading, of course). Today, printers will become obsolete, simply because they change so fast that nobody can keep up to the changes, and people are starting to realize that it is faster, and easier, to view things on the screen. Portable screens also make that much easier.

1369
A new demo CD has been uploaded last night that also has the latest Realtek 0.3.1. driver onboard
that should fix the problems with the Realtek driver.  As reported previous news postings most issue's with OS2AHCI, danis506.add and USB stack should be resolved now. But we would like to know if it now works for everybody that reported bugs.

I have tried this on 5 machines. The results are pretty good. It boots on every one, and it will connect to the internet on all of them (including 3 that had troubles with the older Realtek driver). The USB problems seem to be fixed, as are the Danis driver problems. I did not see a problem with OS2AHCI, but the new one didn't break it.

I think the demo needs more variety in the sample programs. Perhaps a JAVA photo editor of some sort, and a simple word processor like FocusWriter.

Quote
3, the desktop looks plain and can't attract new comers.

Anybody who really cares about how it looks, is going to be disappointed. EComStation will probably never look like windows, but it is also unlikely to ever be under attack by viruses. I guess it depends on what the potential user is really looking for.

1370
Applications / Re: wpa_supplicant v2.0 for OS/2
« on: May 14, 2013, 07:29:48 am »
Quote
Feedback appreciated!

Your work is also very much appreciated. Thanks.

On my IBM ThinkPad T43 (1871-W8M with Intel 8086:2915 device, run by GENMAC), it works the same as earlier versions (very well), when using WPA-PSK. It still won't connect if I try to use WPA2-PSK, but WPA-PSK is rock solid.

Trying WPA2.PSK produces:
Code: [Select]
Successfully initialized wpa_supplicant
lan1: Trying to associate with SSID 'DougB'
lan1: Could not read SSID from driver
lan1: No network configuration found for the current AP
lan1: CTRL-EVENT-DISCONNECTED bssid=00:00:b8:fd:29:00 reason=3 locally_generated=1
lan1: Trying to associate with SSID 'DougB'
and it never connects. I suspect that it may be a GENMAC problem.

1371
Applications / Re: libusb-1.0 port to OS/2 - help needed
« on: April 26, 2013, 06:47:30 pm »
7 systems. LSUSB works as described on all of them.

Sorry, no USB scanner to work with.

1372
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 09, 2013, 08:07:17 pm »
I think that Lars has been doing great work with the USB stuff. However, it seems that the poorly written, and even more poorly followed USB specs are causing problems for him. Throwing in "unusual" devices, like a trackball, doesn't help. It may become a case where users will need to mix, and match, the different parts to find a combination that works. At least Lars is willing to continue trying.

GENMAC also has some very strange problems (that likely won't get fixed), but I haven't seen any evidence that either driver will interfere with the other (doesn't mean that it doesn't happen).

ECS 2.2 beta seems to have picked a couple of bad combinations of both of those drivers, and there are some other problems that may affect what you are seeing. Right now, I am waiting to see what the next beta does. The current one seems to have a number of problems, that have been identified, but working around one, may be causing others to show up. It becomes a chicken and the egg problem, which can waste a whole lot of time.

1373
Utilities / Re: Innotek font engine
« on: April 06, 2013, 05:09:29 pm »
So, the best thing to do is always to leave it in LIBPATH and delete the regedit entries?

I think it would be better to simply change the "enabled" entry from 1 to 0, for all programs that are listed. As near as I can tell, there are possibly 3 places in the registry that are affected. It depends on which version(s) of font engine you have ever installed. ]

It is essential to NOT use the font engine with the later Mozilla derivatives, They do that themselves, and doing it twice is a sure to cause problems. NOTE that OpenOffice, apparently, uses the fontlib support, but OpenOffice should not be set to use the fontlib.

To make it simple, there is a GUI app that adjusts those entries for you. It says it is a beta, but it seems to work well:
ftp://ftp.netlabs.org/pub/vxapps/ft2gui/ft2gui20beta3.wpi

1374
Quote
- ACPI - I have to use the /VW switch on the Samsung Slate, otherwise the boot process stops with "Can not load OS2AHCI.ADD because IRQ 19 allready claimed" -> so obvious for me tha the handling of hig IRQ is not working as it should as eCS 2.1 with ACPI 3.21.07 does not have this problem (but some more I do not have with Warp 4). I only have the ACPI32107.wpi file installed, no more ACPI related files. Do I need something else to handle the high IRQ in the right way?

ACPI32107 seems to work very well. Your problem is probably one of the system drivers causing problems, or it may be something in the BIOS that is claiming IRQ 19 before ACPI gets started. Either you aren't starting ACPI properly (at the right time), or you need to figure out what is holding IRQ 19, and do something about it. On the other hand, is there really any reason to not use /VW?

Quote
- Atheros WLAN - I still try to figure out to run the Atheros WLAN 9285 chipset. I already opened the Slate and could change the MiniPCIE Option GM67 card, and put an Intel inside, but I would loose Bluetooth or 3G,a s there is no Intel chipset Mini PCIE card around with Bluetooth, Wlan and 3G - I do use and need all three for windows. And I am not sure if the WLAN Multimac for Intel will see the light of the day (hopefully it will). Someone posted to me a mail with some hints for this card (I already got the driver loading in UNSUPPORTED mode but the boot process stops - I guess because of netbind.exe or an IRQ conflict) - but unfortunately I lost this mail. May be thsi person is reading here and can send it to me once again?

If you want to use an UNSUPPORTED wireless LAN device (any of them), you need to patch \IBMCOM\macs\GENM32W.OS2. Apparently, GENMAC does not enable the piece of code that XWLAN needs to interface with the windows driver, if you use UNSUPPORTED mode. See the GENMU_TEST_README.TXT file at ftp://genmac@ftp.os2voice.org/ (use the word "unsupported", lower case, and no quotes, as a password if asked), for more information. Also check that for the presence of an already prepared driver. I don't know what the PCI ID for that device is, and it may already be included. If not, supply the parts, and I will add it to the TEST version. The instructions are in the README. I can't guarantee that it will actually work, but it should get installed properly that way (including the required patch).

Quote
- Memory management - the Installation "only" sees 512MB of the internal 4GB of RAM - according to the xworkplace program "OS/2 kernel" - as it is an Intel Core i5 second generation cpu the same problems occur with eCS 2.2 beta. Is there a program that can show me the amount of space OS/2 "really" uses or sees?

It seems that all UEFI machines are going to have this problem, to some extent. Somebody decided to allow more than one memory hole, and OS2LDR can't handle that. It also seems that 512 meg seems to be a popular spot to put the second hole. That means that OS/2 (eCS) can't assign memory above that address. OS2LDR needs to be fixed, somehow. From what I can tell, OS/2 "sees" 512 meg, and no more. Since OS/2 can actually operate reasonably well with that amount of memory, you will probably find that the machine will work okay, and hope they can fix the problem, eventually. Changing video cards is not a viable work around for most machines (especially laptops). I expect that what Roderick describes simply moved the memory hole to another spot. In my case, on my Lenovo ThinkPad L530, I think it is one of the NICs that sets up shop at 512 meg, not the video card.

Quote
The user continues make damage to eComStation (and eComStation.RU)

eComStation.RU does their own damage. They don't need any help from Sigurd.

Quote
The problem is simple - IBM (eCS) OS2LDR gets only 1st block of memory from system, but EFI BIOS split memory on 2-3 huge blocks...

Apparently, it is not always "huge" blocks, and it can be more than 2-3. It depends on the specific system, and what I/O they have installed.

Quote
Because if this would be an EFI issue and you insert a different video card and the memory hole then goes away!?

It is definitely a UEFI problem. The UEFI specs allow for I/O devices (not just video cards) to put holes in memory, and it seems that those holes can be put anywhere they please. Logically, they should be at the end of memory, but that is not in the specs. It also seems that Microsoft defined the specs, and saw an opportunity to mess up other operating systems, again. Linux has, apparently, found a work around, but it is not that easy in OS/2 since they do not have the source for OS2LDR (or, if they do, it is not common knowledge).

I have yet to see any way to "insert a different video card" in a laptop. It can also be difficult in a desktop, sometimes. Not to mention it is an extra expense that many people aren't willing to pay (eCS is not cheap to start with). The problem needs to be fixed, soon, because UEFI seems to be the way that all new hardware is going.

1375
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 04, 2013, 06:04:43 am »
I decided to tackle my old test machine. The machine has a CD drive, not a DVD drive. It also seems that it is difficult to find an IDE DVD drive. So, I got a USB DVD drive.

The first problem is that the machine will not boot from a USB CD/DVD drive. Okay, I made the diskettes. After remaking one bad diskette, I got it to boot, and loaded all four diskettes. It asked for the driver update diskette, which I didn't try, but also gave me a message that the code had not loaded properly, for some reason. Okay, I pressed a key, and the preboot menu showed up. So, I proceeded. The install started, and came to an abrupt halt, when the disk drive could not be "seen". The Dani driver problem (I thought somebody said that only affected a few laptops). So, start over, and select the IBM1S506 driver. Now, the USB DVD drive could not be read. After I powered everything off, and started again, the USB drive was okay, so I proceeded. All went well until it did the first reboot. Now, the USB drive could not be read, again. Okay, I know that is one of the symptoms of the USB drivers, so I rebooted to an alternate boot system, and put the 186 USB drivers in. While I was at it, I put the Dani driver, and DaniFLT.FLT, from eCS 2.1 in and changed the CONFIG.SYS. Rebooted again, and off it went, for a couple of minutes. Then it stopped. No indication of any problems, but it was going nowhere.I realized that I had forgotten to REM the NTFS.IFS and HPFS.IFS lines in CONFIG.SYS, so I rebooted, did that and rebooted again. It continued, and now I am waiting as it is apparently installing CUPS. I think i will kill it because it should not take that long, even if it is downloading it. Hmmm. It took the rest button to break it loose.

More about this saga, if I ever get the time to do it.

1376
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 04, 2013, 05:14:45 am »
Quote
I'm seeing the occasional problem of the system boots to a working Desktop but the USB mouse is totally unresponsive,

This is one of the symptoms that the USB drivers can cause. I have reverted to the 186 version, and have had no more problems with that sort of thing.

I have noticed that boot times seem to be shorter with eCS 2.2 (once I get it going properly). I haven't actually timed it. If you are seeing a problem at the time the logo is on screen, it could be a number of things. The most likely, is that BootDly.SYS is inserting a ridiculously long delay after a SCSI driver is loaded. Inspect your CONFIG.SYS for such a thing. AFAICT, the delay may be needed if you boot from a SCSI device, otherwise, it is not really needed. Some experimenting may be needed to find a more reasonable delay, if it is needed at all. My SCSI card runs my scanner. No delay is necessary for that.


1377
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 03, 2013, 06:10:36 pm »
Quote
The way Q&A work has been done at Mensys has never been realy been different for the last 10 years since I have always done this.

We noticed. It has always been "late", and the end result has always had more problems than a user would expect. This was not unexpected in early releases, as everybody was learning. It is becoming more irritating because the record isn't getting any better. It is still "late" and there are still more problems than expected. Some of the problems are not really unexpected, but you (or somebody in the team) knew about more than one of them, before the beta was released. That should have stopped it, or you should heave gone back to what is known to work for the majority. I would also suggest that announcements of new public betas should not take place, until you have one, in hand, that works for your testers (obviously, you need more testers, to do Alpha testing), Then, the only changes that get made, would be to correct a found problem, then the beta test starts over again. When all of your testers agree that it works as expected, then you announce a public beta, and nothing changes unless a serious problem is found.

The fact that the wrong USB drivers got included, on the first download, demonstrates that somebody lost control of the product quality, and/or nobody did proper testing of the product before it was released. Announcing it, then delaying it, demonstrates that you do not have control over the product.

It seems that you need to have a list of machines that need to be tested, including newer and older laptops. Then, you need to know who can do testing for those machines (more than one, when possible - preferably an experienced user, and somebody who is not a techie), and be sure that they test specific parts that have been changed. In many cases, the test only needs to include changing a driver (like Dani), to be sure that it still works, after somebody changes something. Once all of the testers agree that something new works, it can be inserted as a candidate for the next beta, or GA. At that point, if somebody wants to change something, they (or you) need to make a business case for it, and the testing starts over. If it passes, it goes into the next release. If not, it goes back for repair, and the testing starts all over again. As soon as a product is deemed to be stable, it gets packaged as a beta, is tested by the testers, THEN you announce a new beta, or GA, and NOTHING changes. If somebody finds a problem, the process starts again.

Once a Public beta has been announced, the next Alpha cycle starts. Any new changes go into that, not into the current beta, which gets repaired only (nothing new), and eventually becomes the next GA, after found problems are repaired, and everybody (including the person who found a problem) agrees that it works as expected.

I am not saying that EVERYTHING needs to be fixed for any specific beta, or GA. You should be able to make an exception list, with known problems, and work arounds, when possible. From that information, a user can make a more intelligent decision about whether to participate, or not. Blindly falling into a problem that can disable a NIC (even in windows), without warning, is not going to impress many people. There will, of course, always be new hardware, or somebody will introduce a new program, that will surface problems that did not get caught, but they should be pretty rare.

1378
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 02, 2013, 08:00:54 am »
Quote
s for the USB drivers. The beta was not released of eCS 2.2 until all issue's where traced and fixed on our equipment. We had 1 system that would hang on the USB drivers after the last device driver was loaded, this delayed the beta release with 3 days. Just like ACPI the USB drivers have been tested on very broad range of systems. Also the USB drivers shipped in eCS 2.2 beta are not 100% the same compared to Lars Erdmann his drivers. The drivers had been slightly modified by David and tested on his 10 systems at home.  Also all systems in the Mensys office where used to test the USB drivers and to test booting from USB CD ROM (another 30 systems or so). And all these systems are of different brands and chip sets BIOS makes etc.

I hate to have to point this out, but Lars knew about the problem with USBEHCD.SYS, days before the release of eCS 2.2 beta. Obviously, somebody decided to ignore the situation. Whether the beta should have been delayed, yet again, or released with the far more stable 186 version of the USB drivers, is a decision that needs to be made. It is true, that a few people had problems with version 186, but they were far fewer than those who had trouble with the 189 version. Then, if you made other changes, that were basically untested by those who did have known problems, I don't feel sorry for you at all. You deserve all of the flack that you are going to get.  I do feel sorry that eCS users don't have a good product to test.

Quote
Sadly the Realtek dossier is far from simple.  And eCS 2.1 also had the same issue!
That the old driver from 2.1 works for you has serious issue's and would cause kernel traps on other systems.

Fair enough, but that is no excuse for releasing a driver that was known, days before release, to have a very serious problem on some systems. I have two systems with different Realtek NICs, and both of them experienced the problem where the interface was disabled, until I did a full power off to get them reset. FWIW, the only driver that works with the Realtek 8168 in my Lenovo ThinkPad L530, is the old RTGNDA driver, which is not included with eCS 2.2. It is not perfect, but working most of the time, is a lot better than not working at all, and causing serious problems that the average user would have no idea what to do about.

In fact, I haven't got around to checking the on board Realtek 8168, that died the first time I tried the old r8110 driver (it was new at the time). The symptoms were exactly the same. It had been working with the GENMAC driver before that (with a few problems). It may actually work if I enable it, and load a good driver in it.

Quote
Realtek makes a complete and utter total mess of its cipset and PCI id's it uses.

I realized that a couple of years ago, yet you recently recommended Realtek NICs. When I got the L530, I found no place where they mentioned the wired NIC chipset. I specifically got an Intel WiFi, looking forward to support from Multimac. If I had realized it had a Realtek wired NIC, I probably would not have got it. My older T510 has an Intel wired NIC, and a Realtek WiFi, which is also waiting for Multimac. I guess I will get the T510 repaired (something died in the power control circuits), and switch the Intel WiFi with the Realtek one. The L530 has other problems, so it might as well be totally useless, and live in the windows world.

FWIW, The WiFi in the L530 is an Intel 8086:0891. I can get GENMAC to load three windows drivers, and they all seem to work, but I can find no way to get the radio turned on (there is no physical switch). It acts exactly like a wired NIC with the cable disconnected. I can load the driver, assign an IP address with IFCONFIG, and I can PING it, but that is the end of the road. I think there are a number of other machines, with Intel WiFi NICs, that have the same problem.

Today, I also observed a very interesting phenomenon. I was doing some big file copies, using SAMBA client on the machine with a Realtek 8169 chipset, and the r8169 Multimac driver. It was doing a sustained data transfer at about 9,000 KB/s. At the other end was a SAMBA server running with an NVIDIA chipset, and the Multimac driver. I then started up an RSync data transfer, using the L530, with a Realtek 8168 chipset, and the RTGNDA driver. It was running happily at about 32,000 KB/s, to the same NVIDIA  chipset, which was happily handling about 41,000 KB/s data rate. This is, of course on a 1 GB network. Looking on the internet, it is suggested that a 1 GB network should be able to run near 60,000 KB/s. In fact, my antique IBM ThinkPad A22e, running an Intel 100 Mbs NIC, runs at  sustained speed of about 8,000 KB/s. There is a serious problem with the Realtek Multimac driver, which needs to be fixed, since it seems to be a popular brand with many manufacturers using it.

1379
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: April 01, 2013, 06:08:42 pm »
Quote
Please note: we have discovered that GenMAC is failing to install properly, which explains most if not all of the networking problems people have experienced after installation. 

Well, that is not the only network problem that exists. It is also not the most serious.

WARNING: If you install using the Multimac r8169 driver, supplied with eCS 2.2, it may disable the interface on your NIC. The symptom is exactly the same as if you had pulled the cable. The BAD part is, that the interface will not enable again (even in windows), until you remove ALL power from the NIC. On laptops, that usually means power off, pull the plug, and remove the main battery. On desktops, it means power off, and pull the plug. After a minute, or so, turn it all back on, and it should work again until you try the bad driver again. Then you start over.

Apparently, this does not affect all Realtek NICS, but I have at least two of them that have the problem, and I know of one other case where it has happened..

Many users are going to have the problem, and assume that eCS 2.2 has killed their NIC. At the same time, they will not be able to get on the internet to find out how to recover from the problem.

This problem existed before eCS 2.2 was released, and David A. (at least) knew about it. That driver (along with a few others) never should have made it into the eCS 2.2 beta.

1380
Article Discussions / Re: eComStation 2.2 Beta First Impressions
« on: March 31, 2013, 07:44:00 pm »
Quote
Well the first hint the Q&A has taken place quite extensively is in the fact we first wanted to release the beta at the beginning of December and we where 3 months later.

I think you don't understand Quality Control. The first rule is to take action to be sure that nothing can go wrong. The second is to be sure that nothing did go wrong.

One thing that you could do, is create a database of files, versions, and file dates, for all files included on the CD/DVD. Use a program to verify that only files that have been verified to be working properly are included. If the program finds some other file, it needs to be thoroughly investigated, to find out why it is there. If it should be there, and has been verified to work properly, the database needs to be updated (then, you need to find out why the database didn't get properly updated). If it shouldn't be there, it needs to be replaced by a file that should be there, or it needs to be removed (and whoever put it there needs to have their hand slapped). Doing that would save many hours of testing, and problem analysis, when a wrong file gets inserted somehow. I would expect that it should be up to the file owner, to get the proper file submitted, along with the supporting documentation, and a statement that they consider the file to be stable. Then, somebody else needs to check it out, and put it into the master file repository, and update the database, when appropriate.

In the eCS 2.2 installer, it is obvious that the USB problems could have been averted, and the Dani driver problem probably could have been averted, without anybody actually having to spend an hour to install on a machine that might be affected, then spending another hour to try to figure out what is wrong. I expect that other problems may have been caught too.

Quote
It's stored in the object setup string.  I don't think there's actually a GUI option to set it, although you can use a Setup String object (from the Templates folder) to try setting "DEFAULTVIEW=DEFAULT;".

OTOH, I just tried this and the results were... inconsistent, to say the least.

However, I've just suggested another possible solution in your ticket #3403.

Your suggestion from ticket #3403 seems to work, but I haven't used it much. I think I will leave the Setup String alone. If somebody comes up with a proper way to return to the old way of doing it, it would be good to automate it. I suspect that many users will find Split View to be "entertaining", but not very user friendly.

Quote
Not my decision...

I know. I won't speculate on who might be responsible for the decision, but it is obvious that they were working with incomplete information, or it would not have been done.

Pages: 1 ... 90 91 [92] 93 94 ... 97