From: Tinka on 12/19/2002
Hello, I was trying to installing winXP in my computer this week. I had win98 then in C: and would want to keep it and install winXP in E:. After install files were copied, the computer was restarted but then an error occured, and I got to know I needed to disable my Goback (made by Roxio)to avoid this error. So I disabled my goback, but then I couldn't enter my win98 anymore. I booted it from the floppy and could only go to DOS. And what surprised me was that under DOS, I only found my C: (4G) and couldn't find D: (10G) and E: (6G), however, it could detect that my whole disk is 20G (which is correct). I had it in my other computer as the slave disk, I still couldn't find D: and E:. And Goback can't be enabled either. So anyone knows how to find out my D: and E:? Has anyone met such situation too? I would be so appreciate for any info provided.
| |
Votes:
Rating: 0
Delete: 0
|
|
--- Replies to this Problem ---
From: deweypalla on 09/15/2003
hi. i had the same problem myself.
i have a primary hdd partitioned between c & d. both used to be protected
by goback 2.1e. i installed linux on a second drive and same thing,
i can only see drive c in linux but not drive d.
the goback site told me to run gb_prog from a windows boot manually.
only this time, goback says it can't find the data file.
i've been scouring the web for answers since and i couldn't find any.
so i ended up copying my drive c files to another hdd and said
goodbye to a year's worth of data on what used to be my drive d.
there. now i know better.
i'm enabling goback on my primary hdd only. i'm keeping it away from
my second fat32/ext (linux) drives altogether.
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Computerpilot on 12/26/2002
If Windows does not recognize a hardware device, it is likely that the device was not properly installed or is malfunctioning.You may try booting your computer with a Win98/98/ME startup floppy and running a scandisk on both drives. If you are unable to access the drives, then you might have a cable or jumper issue. If you have not touched your drives and they worked previously, I would definitely consider them as failed. In addition, if you are able to run a scandisk with the startup floppy and get a few errors, you can also assume that the disks have failed. Computerpilot
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Tinka on 12/19/2002
Thanks Computerpilot. But actually I didn't reach the step where XP installation asked me if I would want to change my drives into NFTS. And I've tried to seached for my D: and E: by using win98, winME and win2000, non of them found my D: and E:. The dual boot for windows had no problem in working before I disabled goback. And my XP actually hasn't been installed yet - only finished the files copying part. So I think the problem must be on the Goback's. //Tinka
| |
Votes:
Rating: 0
Delete: 0
|
|
From: Computerpilot on 12/19/2002
There are quite a few things that could cause this problem. Please keep in mind that Windows 98 CANNOT read an NTFS partition that is created with Windows XP. You would need to reformat the drives to FAT or FAT32 to read them from Windows 98. You can install Windows XP in a FAT or FAT32 parition. This will allow you to go back and forth between disks. However, you cannot 'downgrade' an NTFS partition to FAT32. You can only upgrade a FAT32 partition to NTFS. Therefore, you must reinstall Windows XP with a FAT32 Partition. Setup will allow you to delete the partition and repartition the drive to FAT32. Windows XP will always try to overwrite MBR for Windows 98. You might try editing it to make sure that it gives you the menu options to either boot to Windows 98 or XP. There are numerous articles on Microsoft's support website that you can check out that will give you step by step instructions for installing a dual boot Windows 98 and XP system. Computerpilot
In addition, you may want to check your BIOS to be sure that you have it set to detect Primary Slave and Secondary Slave devices. If the disks do not appear during boot or in the BIOS, you have a connection problem or a problem with the actual drive(s).
| |
Votes:
Rating: 0
Delete: 0
|
|
|
