Need help installing pup on old IBM laptop(solved)
not quite yet
okso I got everything done with no misstypes but I get a "bad command or file name for the bootgrub/grub exe config file...... I think I know..the line reads C: \bootgrub\grub. exe well if the "c" is the drive and bootgrub is the folder on the drive then the command should read c:\puppy\bootgrub\grub.exe because the "bootgrub is in the folder "puppy"
and now for the bad news I can't get back into windows to take bootgrub out of the puppy folder the set up log freezes
okso I got everything done with no misstypes but I get a "bad command or file name for the bootgrub/grub exe config file...... I think I know..the line reads C: \bootgrub\grub. exe well if the "c" is the drive and bootgrub is the folder on the drive then the command should read c:\puppy\bootgrub\grub.exe because the "bootgrub is in the folder "puppy"
and now for the bad news I can't get back into windows to take bootgrub out of the puppy folder the set up log freezes
I'm just a passing thought in this world
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Reboot the Thinkpad. While it's rebooting, keep tapping, about three times every two seconds, the F8 key. This will bring up a Microsoft Windows 95 Startup Menu. One of the choices on it is "Safe mode command prompt only." Choose this. This will bring you to a C:\> or C:> prompt. Issue the command
edit c:\autoexec.bat
and you can change the line to read puppy\bootgrub instead of bootgrub.
To save go Alt File Save and then Alt File Exit.
Reboot.
If that doesn't succeed in booting Puppy, then do the F8 bootup again and choose
Step-by-step confirmation.
This allows you to step through the bootup process, one line at a time, and watch carefully for error messages. You can see this way which line sends things off into space.
edit c:\autoexec.bat
and you can change the line to read puppy\bootgrub instead of bootgrub.
To save go Alt File Save and then Alt File Exit.
Reboot.
If that doesn't succeed in booting Puppy, then do the F8 bootup again and choose
Step-by-step confirmation.
This allows you to step through the bootup process, one line at a time, and watch carefully for error messages. You can see this way which line sends things off into space.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
no, this is what it said
C:\>ECHO Welcome to the pup Pelokwin
Welocome to the pup Pelokwin
C:.PAUSE
Press any key to continue...
C:\>break on
C:\>C:Puppy\bootgrub\grub.exe --config-file=(hd0,0)/bootgrub/menu. lst
cannot run in protected mode. must run in real mode
c:\>goto theend
C:\>rem end of pelokwin's c:\autoexec.bat modified by Sit Heel Speak
c:\>
c:\>
c:\>
c:\>
C:\>ECHO Welcome to the pup Pelokwin
Welocome to the pup Pelokwin
C:.PAUSE
Press any key to continue...
C:\>break on
C:\>C:Puppy\bootgrub\grub.exe --config-file=(hd0,0)/bootgrub/menu. lst
cannot run in protected mode. must run in real mode
c:\>goto theend
C:\>rem end of pelokwin's c:\autoexec.bat modified by Sit Heel Speak
c:\>
c:\>
c:\>
c:\>
I'm just a passing thought in this world
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Ah. You only changed "bootgrub" to "puppy\bootgrub" once. You also need to add "puppy" in front of "bootgrub/menu.lst" as well.
At the C:\> prompt, issue the command
edit autoexec.bat
and change the line to
C:\Puppy\bootgrub\grub.exe --config-file=(hd0,0)/puppy/bootgrub/menu.lst
Alt-File-Save and try rebooting with that.
At the C:\> prompt, issue the command
edit autoexec.bat
and change the line to
C:\Puppy\bootgrub\grub.exe --config-file=(hd0,0)/puppy/bootgrub/menu.lst
Alt-File-Save and try rebooting with that.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
I am beginning to suspect that the drive is still compressed. When we were done last night, did you turn it off? If so, then when you restarted today the first time, before we changed msdos.sys and config.sys to stop the loading of DriveSpace, ...Windows may have remounted the compressed volume, and we indeed may still be inside it.
Try issuing the command
mem /c /p
and see if DRVSPACE appears in the top part, which lists the loaded drivers.
Does it?
Try issuing the command
mem /c /p
and see if DRVSPACE appears in the top part, which lists the loaded drivers.
Does it?
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
OK, then we did succeed in exorcizing the DriveSpace devil. There is something else wrong, something wrong with grub.exe.
Below is my own subdirectory listing, the one where grub.exe is.
Issue the command (EDITED to make it easier on your eyes)
dir c:\puppy\bootgrub /on /p
(hit the enter key if you need to scroll the screen)
and tell me if your grub directory looks similar to mine (except, yours won't contain vmlinuz and image.gz):
Below is my own subdirectory listing, the one where grub.exe is.
Issue the command (EDITED to make it easier on your eyes)
dir c:\puppy\bootgrub /on /p
(hit the enter key if you need to scroll the screen)
and tell me if your grub directory looks similar to mine (except, yours won't contain vmlinuz and image.gz):
- Attachments
-
- Sit Heel Speak's grub.exe DOS directory.png
- (23.4 KiB) Downloaded 683 times
volume in drive c has no label
volume serial number is 1625-0ef3
Directory of C:\PUPPY\BOOTGRUB
. <DIR> 04-19-06 5:04A
.. <DIR> "same as above"
GRUB EXE 105,482 04-11-06 11:26P
MENU LST 201 04-19-06 10:39P
2 files 105,683 bytes
2 dir(s) 1,250,525,184 bytes free
C:\>
that is all it say's
volume serial number is 1625-0ef3
Directory of C:\PUPPY\BOOTGRUB
. <DIR> 04-19-06 5:04A
.. <DIR> "same as above"
GRUB EXE 105,482 04-11-06 11:26P
MENU LST 201 04-19-06 10:39P
2 files 105,683 bytes
2 dir(s) 1,250,525,184 bytes free
C:\>
that is all it say's
I'm just a passing thought in this world
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
I think we're closing in on the problem now...
grub.exe must need some of those other files.
Reboot, don't tap F8, choose the "Windows" menu option, and tell me if Windows 95 comes up OK.
Meanwhile, I'm going out on the 'net and track down exactly where I got my "full-fledged" copy of grub from. Back in a few minutes.
grub.exe must need some of those other files.
Reboot, don't tap F8, choose the "Windows" menu option, and tell me if Windows 95 comes up OK.
Meanwhile, I'm going out on the 'net and track down exactly where I got my "full-fledged" copy of grub from. Back in a few minutes.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
The grub I'm using is
grub_for_dos-0.4.2pre4.zip (1,218,986 bytes) (EMM386 support)
First issue the command from a DOS prompt
copy c:\puppy\bootgrub\menu.lst c:\
and then download the above zipfile from
http://grub4dos.freespaces.com/
then unzip it to a fresh new temporary directory C:\ZIPTEMP
and burn the whole directory, with its subdirectories, to CD,
then copy it onto your Thinkpad's c:\Puppy\bootgrub subdirectory, entirely.
You can do this by opening two instances of Windows Explorer, one on the CD and the other on C:\Puppy\bootgrub,
and using Ctrl-drag'n'drop,
or,
you can do it from the MS-DOS prompt, by issuing the command (if I recall, your CD is Drive D:)
(let's say that grub.exe is in D:\grub4dos)
xcopy /s /e d:\grub4dos\*.* c:\puppy\bootgrub
and then, to restore menu.lst to how you edited it, issue the command
move c:\menu.lst c:\puppy\bootgrub
(answer the "overwrite?" question yes)
I'm going to call it a night. I'll be back here tomorrow night, 10'ish your time.
grub_for_dos-0.4.2pre4.zip (1,218,986 bytes) (EMM386 support)
First issue the command from a DOS prompt
copy c:\puppy\bootgrub\menu.lst c:\
and then download the above zipfile from
http://grub4dos.freespaces.com/
then unzip it to a fresh new temporary directory C:\ZIPTEMP
and burn the whole directory, with its subdirectories, to CD,
then copy it onto your Thinkpad's c:\Puppy\bootgrub subdirectory, entirely.
You can do this by opening two instances of Windows Explorer, one on the CD and the other on C:\Puppy\bootgrub,
and using Ctrl-drag'n'drop,
or,
you can do it from the MS-DOS prompt, by issuing the command (if I recall, your CD is Drive D:)
(let's say that grub.exe is in D:\grub4dos)
xcopy /s /e d:\grub4dos\*.* c:\puppy\bootgrub
and then, to restore menu.lst to how you edited it, issue the command
move c:\menu.lst c:\puppy\bootgrub
(answer the "overwrite?" question yes)
I'm going to call it a night. I'll be back here tomorrow night, 10'ish your time.
I was also seeing double alright so I just wanted to give you some more info befor I started putting the new grub file in. when I first try and boot puppy from the HD I get a msg. that says--
EMM386 successfully installed.
Expanded memory services unavailable.
Largest upper memory available.............122kb
Largest upper memory Block available.....95kb
upper memory starting address..............c800 h
EMM386 active.
um... mean anything to you? well i'm going to start so ,I HOPE, the next post is one word "WE GOT PUPPY ON THAT OLD IBM THINK PAD!!! ok mabey 8 words
EMM386 successfully installed.
Expanded memory services unavailable.
Largest upper memory available.............122kb
Largest upper memory Block available.....95kb
upper memory starting address..............c800 h
EMM386 active.
um... mean anything to you? well i'm going to start so ,I HOPE, the next post is one word "WE GOT PUPPY ON THAT OLD IBM THINK PAD!!! ok mabey 8 words
I'm just a passing thought in this world
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
The "/v" switch which I added makes EMM386 display the messages ("v" stands for "verbose"). The messages tell us that EMM386 has successfully loaded. The "Expanded memory services unavailable" part means that we specified NOEMS in the command line, just as you were doing before--in other words, EMM386 is managing memory through the Microsoft "extended memory specification" method rather than the older Microsoft "expanded memory specification" method, which was a 286-era kludge. EMM386 is running fine.
Try the "reboot-and-tap-F8" routine and choose Safe Mode. Tell me if that brings up Win 95 (in 640 x 480 VGA mode).
Try the "reboot-and-tap-F8" routine and choose Safe Mode. Tell me if that brings up Win 95 (in 640 x 480 VGA mode).
no it went to a comand prompt the page looks like this
windows start up menu
1 normal
2 logged (\bootlog txt)
3 safe mode(this is what i picked
4 safe mode with network support
5 step by step config.
6 comand prompt
7 safe mode comand prompt
enter a choice _
windows is bypassing your start up files
HIEM is testing extended memory...done
C:\>
windows start up menu
1 normal
2 logged (\bootlog txt)
3 safe mode(this is what i picked
4 safe mode with network support
5 step by step config.
6 comand prompt
7 safe mode comand prompt
enter a choice _
windows is bypassing your start up files
HIEM is testing extended memory...done
C:\>
I'm just a passing thought in this world
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind