AuthorTopic: VL-5.9-STD-RC1.3 (Read 31912 times)

It is possible to create an application like the current vasm in gambas2, using Text mode if GUI is not available and using GUI when X is running... but there is so much in vasm that I dont know... lots and lots of scripts... all of which would have to be re-worked to fit the new purpose.

That sounds to me like too much work for the small gain. I've never minded the looks of VASM in either text mode or the GUI version. It's plain, sure, but it's fully functional and easy to use.

Developer time might better be spent on something else. It would be nice to have a pretty VASMCC, though.

What I'd really like to see is an easier way to set up wireless. I was impressed with the GUI setup in PCLinuxOS and Mandriva One. I wish we could have something similar just for wireless (VASM is fine for the other stuff). It wouldn't need to be fancy; a text-look would be fine. It should just make it easy to set up everything needed for making a connection step by step, including a way to assign a fixed IP address, and a way to set up wifi-radar. Also a way to make the connection automatic whenever you start your computer, if that's what you want.

As it is now, I have to start wifi-radar whenever I start XFce, then I have to tell wifi-radar to disconnect, then tell it to connect. I don't understand why I have to disconnect with wifi-radar when it first starts and then tell it to connect. I suspect it has something to do with DNS, but I already have my connection's DNS server entered in VASM's wireless connection section and in wifi-radar.conf.

If we're concerned about new users, I think VL needs to make WPA wireless easier.--GrannyGeek

I think I just have confirmed that, as reported earlier I can't print with kernel 2.6.23.1.I replaced it with kernel 2.6.21.1 and whoom, what was in the print queue was printed when I rebooted. I changed back to 2.6.23.1 and nothing is being printed again. Rebooted twice just to make sure, nothing doing.Needless to say in between the changes I do the lilo bid.

My Epson LQ300 printer is connecetd to an USB port. Could that be the problem for kernel 2.6.23.1?

I installed RC1.3 on my Celeron desktop and had some problems. With the linux kernel option it didn't see my floppy drive or my sound card (a VIA AC97 that has always worked with earlier Linuxes). So I reinstalled, this time using the linux2 kernel. This time it did see my sound card, but still no floppy drive is recognized.

Other than that, it's fine so far. I'm a bit alarmed, though, because I've never had a problem with any hardware on this desktop and have installed every version of VL from 4.whatever Standard to RC1.3, including several betas for 5.8 Standard, and this is the first time I've had hardware recognition problems.

I almost forgot--when I tried to select a /mnt/win partition during installation, it didn't show my FAT32 partitions, only my NTFS partitions. I had the same thing happen on my Turion laptop--only the NTFS partition was offered for /mnt/win during installation. On both computers I was able to add all my partitions through VASM once VL was installed and running.--GrannyGeek

I almost forgot--when I tried to select a /mnt/win partition during installation, it didn't show my FAT32 partitions, only my NTFS partitions. I had the same thing happen on my Turion laptop--only the NTFS partition was offered for /mnt/win during installation. On both computers I was able to add all my partitions through VASM once VL was installed and running.

As a matter of curiosity, were you able to add NTFS partitions with VASM? My attempts to do so have ended up with them being set up as XFS instead of NTFS. I'm wondering if this is a general problem or something to do with the strange partitions on my laptop - It currently has XP Pro, OS/2 (one copy current, one copy beta), two versions of Zenwalk (1 4.8 plus, one Snapshot) plus VL 5.9 RC1.3. I use XFS for most of my Linux partitions, and have both HPFS and JFS partitions for OS/2, so I'm not sure whether the multitude of file systems may be confusing VASM...

Yes, I had no problems adding NTFS partitions with VASM. On one computer I have one NTFS partition; on another I have three NTFS partitions, three FAT32 partitions, and two other Linux partitions formatted with reiserfs.

I did have an odd problem with some 5.8 Standard betas. VASM identified one Windows partition as reiserfs. I think it was FAT32 (can't remember for sure). I went ahead and had VASM mount it with the noauto option and then I'd fix it up in /etc/fstab. It was odd, though, that it was identified as reiserfs. I think it was a bug that got fixed somewhere in the beta cycle.--GrannyGeek

I made a new install, this time with linux2. All went well and the problems reported earlier still exist among them:

First startx gives a black screen with a terminal in the left upper corner. Can get out of it only with Ctrl-Alt-Backspace. After assigning a desktop with xwmconfig, xfce4 or others will start properly.

Printing with kernel 2.6.23.1 ist still impossible. I do a lot of printing, that would be a no go.

This is the first VL version that dependably shuts my computer completely off. Other versions would boot down, shut down the HD's but not shut off (most of the time). I would have to tweak my LILO to correct before.