Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to think back to my Windows days. That "loading windows" part, is that on a graphical display (Windows logo is present) or a text display (black screen with plain white text)? I seem to remember this text coming up AFTER the Windows graphic logo is displayed. If so, then you can try booting Windows in "safe mode". It could be trying to load some driver and hanging. In safe mode you can stop drivers from loading and get some debugging done. Sorry, I've been away from Windows and do not remember the key combination you press at boot time for force safe mode. My mind is drawing a blank right now. I'll probably remember it right after I submit this post! Try a Google search on "Windows safe mode"
Anyway, I don't know why you might be having a problem with a driver after copying stuff to your D: drive. Unless the driver or some file it wants to read happened to be on D: before you wiped it out. Usually drivers would be on your C: drive. Are you sure you didn't sneak in a little copying to your C: drive while you were trying to get stuff to your D: drive?
My previous post, referring to WIndows multibooting, would not apply to you. If you're only running Win98. Microsoft did not introduce their multibooting until W2k.
after selecting "win" from lilo menu
i see a black screen and in the top-left corner a message...
i'm pretty sure that did'n write to C: - i copied files several times and used the same dir...
/mnt/usb-storage/net/backup
OK. I was thinking your message was comming from Windows. I don't think so now. It's coming from LILO.
Unfortunately, I know Grub, not LILO. There are a lot of LILO users here that could better help you debug than I could. Hopefully one of them will chime in...
yeah well now that you mention you have w98 I will change tactics.
Can I suggest that you download some free (GPL) bootable live cds
The closest to W98 is www.freespire.org has nvidia and ati graphic drivers by default and win codecs.
The bigger live cd is knoppix either as a cd or dvd....yep dvd.
If your hardware is really old and can not handle hi graphics or has small ram like 64 Megs try Damn small linux.
Put it this way. If your Win98 cannot be booted by Lilo, after retoring Lioo properly and has it confirmed "Windows added" then may be you have damaged the Win98 partition.
The proof of a pudding is in the eating so why not retore MS's MBR, boot up a Dos floppy with fdisk.exe inside and type
Code:
fdisk /mbr
Now you are only dealing with a 100% MS system. Tell us if it boots.
I am with many posters here in thinking technically writing whatever files from a Linux partition to a logical partition in Win98 (Drive "D") should not have any influence to the Win98 housed in the first primary partition.
i disconnect HDD where is linux ( just in case )
fdisk /mbr - and win loads
win loads Ok
i connect again HDD with linux
try to load win - - Fail
The disconnecting/reconecting thing sounds suspiciously related to Window's normal refusal to boot itself off of a second hard drive. I believe Windows needs some help for Linux to accomplish this seemingly trivial feat (not trivial for native Windows however).
I do not know the details. I am simply remembering something I read somewhere talking about "Windows vs. the second harddrive". There is some trick in LILO or Grub (I think) where you can make Windows think it's on the first HDD when it's really on the second. But I can't remember the details, or even if what I'm remembering is relevent. Maybe somehow in the past you had this "trick" in LILO but now it's somehow been overwritten and wiped out?
I'm just guessing at all of this ... trying to help you out ... but I don't want to send you down a bad path because of my failing memories, so I'll shut up now.
You committed a crime in an operating system if you install it in the 1st boot disk and later boot it as the 2nd boot disk. No operating system in the world can accept such a humiliation because the system files would have the addresses all pointing to the 1st boot disk.
Since you use Lilo you can ask Lilo to do a disk swap on-the-fly with these two lines in the section of /etc/lilo.conf that boots Windows
Code:
map-drive=0x80
to=0x81
map-drive=0x81
to=0x80
This is the Lilo's way to switch the 1st and 2nd disk orders temporary. The disks revert back to original positions after you exit Win98.
If you do not know how to edit /ect/lilo.conf to include the suggestion I outlined in Post #26 then paste the content of /etc/lilo.conf here. Also list the content of the Bash command "fdisk -l" which will tell us your partitioning scheme.
I summarize your current situation as
(a) Win98 boots if it is only one hard disk (hda) in the PC
(b) Linux boots when connected as the primary but Win98 doesn't when hooked as the slave.
My advice to you is to connect the two disks permanently and chop off one of your two hands so that the disk order can never change again. Let Linux deal with the problem using software. Pulling hard disk connectors off for booting purpose is an activity belonging to the Dark Ages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.