[newbie] Dumping my 1.4 GB /boot?

2000-09-07 Thread Brisco County Jr.

When I installed Linux Mandrake 7.1 it created a boot partition of about 
1.4 GB, which is now mostly a wasteland. I've since learned that not only 
did it not need to be more than 5 MB or so, starting with LM 7.1 you don't 
even need a /boot partition at all! But in checking it now, it contains 
this small handfull of files:

System.map, System.map-2.2.15-4.mdk, boot.0300, boot.b, chain.b, 
initrd-2.2.15-4mdk.img, initrd.img, kernel.h, map, os2_d.b, us.klt, 
vmlinuz, vmlinuz-2.2.15-4mdk, and finally the Grub folder (which I'm not 
booting with - I'm using LILO).

My question is this - could I create a folder of the same name and put all 
these files into it so that I could finally put this partition to use for 
something else?

Can anyone tell me if this could easily and safely be done? I'd like to 
avoid tampering with my partition sizes if I could. My partition table 
didn't react too well to that the last time I did that. Thanks!!!





[newbie] Wine: It works! (Mark)

2000-08-31 Thread Brisco County Jr.

Thanks Mark - it actually worked! So far I've only tried the method of 
clicking on the .exe from the file manager and specifying to open with 
Wine, but I'm going to experiment. Couldn't get most of my regular programs 
to work properly - some games complained about the lack of DirectX 6 being 
installed, and many others seemed to think that they had just been 
installed - I guess they couldn't find the path to their configuration 
files. Probably all to be expected though, at this point. Sure was strange 
to see them startup in Linux though! Even more strange - one program that 
nearly always crashes Windows when something goes wrong - it locked up, but 
this time all I had to do was "Kill" it!

At 07:05 AM 8/31/00 -0400, you wrote:
"Brisco County Jr." wrote:
 
  Thanks - but here's what it says when I set the path to any Win program:
 
  /usr/x11r6/bin/wine-strip: Can't exec '/mnt/dev/hda1/windows/notepad.exe':
  file not found.
 
  And it also says it couldn't find find my keyboard layout.
 

I've found it to be a normal method of operation for Wine to complain
about the keyboard, however, this usually doesn't prevent it from
working. What IS preventing Wine from finding and executing your request
is your path statement. It WAY wrong. You don't reference your
"partition" identity in the path. If that is a correct representation of
the path on your computer to the Windows Notepad program the path
statement should look like this:

 /mnt/windows/windows/notepad.exe

The full command line command with arguments looks like this:

 wine   /mnt/windows/windows/notepad.exe

 the  | the path statement
 prog |

wine = the program being invoked
/mnt = dir on linux fs where the windows folder lives
/windows = the actual vfat partition
/windows = the windows dir within the windows partition
notepad = the executable desired to be run

Hope this helps,
--
Mark





Re: [newbie] Wine: How to start?

2000-08-30 Thread Brisco County Jr.

Thanks - I get exactly the same results from console! And if I type in a 
path it just says file not found.

At 09:52 PM 8/29/00 -0700, you wrote:
On Tue, 29 Aug 2000, you wroted:

suppose to go to the console and type wine at the prompt.  I couldnt get wine
to work because it couldnt locate the mapping of keyboard.

  Been trying to figure out Wine - how exactly do you use it? I can't get it
  to even start. Thanks





Re: [newbie] Wine: How to start?

2000-08-30 Thread Brisco County Jr.

Thanks - but here's what it says when I set the path to any Win program:

/usr/x11r6/bin/wine-strip: Can't exec '/mnt/dev/hda1/windows/notepad.exe': 
file not found.

And it also says it couldn't find find my keyboard layout.

And when looking at the installed files with the RPM viewer, it says "file 
attribute differences, etc/wine.conf and usr/x11r6/bin/wine-conf.

At 10:48 PM 8/29/00 -0400, you wrote:
wine [/path] /filename.ext

i.e., wine /mnt/dev/hda1/aclt/acltwin.exe

would mount and open autocad lite.  I have had problems
with the files directory associated, but the program opens.
With more work, or copying the necessary files to a directory
in Linux, things should work better.  But that's the general idea.
I'm just fooling with it now, but would like to get all of this
stuff to work, not being all that happy with the MS attitude. . . .
--doug

At 08:36 08/29/2000 -0700, you wrote:
 Been trying to figure out Wine - how exactly do you use it? I can't get it
 to even start. Thanks
 





Re: [newbie] Wine: How to start?

2000-08-30 Thread Brisco County Jr.

Thanks - When I tried that to launch notepad (including the path), it 
responded with:

/usr/x11r6/bin/wine-strip: Can't exec '/mnt/dev/hda1/windows/notepad.exe': 
file not found


At 08:47 PM 8/30/00 +0100, you wrote:
from the shell:

wine windowsprogram.exe

- Original Message -
From: Brisco County Jr. [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 29, 2000 4:36 PM
Subject: [newbie] Wine: How to start?


  Been trying to figure out Wine - how exactly do you use it? I can't get it
  to even start. Thanks
 
 





Re: [newbie] Wine: How to start?

2000-08-30 Thread Brisco County Jr.

Thanks Mark! I'm going to try them tonight!

At 10:37 PM 8/30/00 -0400, you wrote:
THis isn't exactly the text book way to use it, but I found this quite by
accident actually. Open the KDE file manager, or use the one that Gnome
uses. Find an executable on your WIndows partition that you want to run,
right click on the file and from the menu choose "open with". When the
dialog box comes up type "wine" in the field offered and hit ENTER.

Otherwise, open a terminal window, type:

 wine C:\\path to\\program file\\filename.exe

 or

 wine /mnt/windows/progra~1/dir_name/filename.exe

You'll notice that I used a DOS style name convention. You will find that
that will be necessary for directory names and file names that are longer
than 8 characters when attempting to references file names and/or
directory names that have "white" spaces in them. Linux does not support
this as we all know Windows does.

In the first command line example the only reason I used the "spaces" was
to represent a typical Windows style system path statement. And you're not
seeing a typo. When referencing a Windows style path statement you are
required to use "two" (2) backslashes, where you only need "one" (1) front
slash when you're using the Unix path statement style to call the Windows
executable.

Anyhow...that's how it's done.

--
Mark

**  =/\=  No Penguins were harmed   | ICQ#27816299
** _||_ in the making of this |
**  =\/=  message...| Registered Linux user #182496
------------

On Tue, 29 Aug 2000, Brisco County Jr. wrote:

  Been trying to figure out Wine - how exactly do you use it? I can't get it
  to even start. Thanks
 
 
 





[newbie] Wine: How to start?

2000-08-29 Thread Brisco County Jr.

Been trying to figure out Wine - how exactly do you use it? I can't get it 
to even start. Thanks





[newbie] DOSEMU: How to start in 7.1?

2000-08-29 Thread Brisco County Jr.

In LM 7.1 DOSEMU won't start, not even when I'm root. It worked fine in LM 
6.0, although like someone else just recently said, there didn't seem to be 
a way to access a real DOS partition, just a fake one.





[newbie] (OT) Windows 95: the Movie!

2000-08-27 Thread Brisco County Jr.

Here's another one too funny not to pass on to the group!
(Takes bout a minute for the show to start)

http://www.newgrounds.com/portal/view.php3?id=1412





[newbie] (OT) An MS Linux webpage!

2000-08-26 Thread Brisco County Jr.

Take a look at this page, you might be surprised! :-)

http://www.mslinux.org