Recent Posts

Pages: [1] 2 3 ... 10
1
Boot Managers / Re: triple boot dos 6.22, win98 SE and winxp pro
« Last post by Tanzmusikus on August 05, 2017, 23:00:36 PM »
Hello!

What is the problem?
I can boot DOS & WinXP with no problems.

Please describe your special situation!

Best regards,
TM
2
Hi Elmar,

thanks for the hint. Will try that.
Interestingly I managed to successful passed step 1 of hfsprescue by alternating some settings on my system. I am pretty sure the reason for the problem was the fact, that I forgot to disable the option "put hdd to sleep if possible" within the energy saving settings. After I removed that particular setting hfsprescue ran like charm. I was even significant faster (5 hours for 100% instead of 24h for 77%).

Currently I am at step 4 and it seems I can rescue quite a few files.  :D

Thanks again for the support.
Cheers
Carl
3
Yes. Thats the problem.

Create an image with dd and use also the parameter 'conv=noerror,sync'

Best regards
Elmar
4
is there a hardware failure on the hard disk with the corrupted file system?

Hi Elmar,

not that I am aware off. I tried to make an image of that disk using dd und ran into a I/O error. You reckon that could be a sign of an faulty hardware?

Cheers
Carl
5
Hello,

is there a hardware failure on the hard disk with the corrupted file system?

Best regards
Elmar
6
Hi all,

as a newby to hfsprescue I am trying to rescue data of an external disk, which has an somehow corrupted filesystem, which can't be repaired by traditional means (fsck and such).
Running hfsprescue -s1 works fine until it reaches exactly 77,16% (718.46 GB) of the scan.

Then hfsprescue stops reading (according to Activity Monitor) and sits there. I interrupted the process after waiting for a couple of hours.

I restarted hfsprescue -s1 three times (it takes approx 24h to get to that point). Last time I choose the force option. Every time it stopped at the exact same point of the scan.

Any thoughts what to do?

Thanks and best regards
Carl
7
Boot Managers / Re: USB key read-only in DOS.. how to make it writable?
« Last post by Mad7Scientist on July 25, 2017, 05:44:05 AM »
I'm glad to hear that write access can be obtained by using DOS USB drivers after starting with PLOP. I hope I can get it to work!

I'm willing to pay a few dollars for a version of PLOP that allows write access to USB. I put in the plop floppy and booted that with a non bootable USB flash drive in. Then I removed the plop floppy and put in a Windows 98 start up floppy. I selected USB and that failed. It may have been the MBR on the USB drive that printed the error. I pressed any key to continue and it continued to boot up from the Windows 98 floppy. Since PLOP installed a BIOS USB drive interface C: became the USB drive. I started setup.exe from the Windows 98 CD on E: but I found that C: is actually read only so it couldn't do anything.

I assume that Windows NT based operating systems do not require USB write access when starting from the boot loader.

It would be nice if there was a check box to install the USB BIOS interface when booting from a floppy or CD-ROM so that a flash drive will show up as C: when booting DOS from a floppy.

Thanks for making PLOP! Is there a reason for why it has to fit in 60 sectors?
8
I had forgotten to specify that the problem came after switching to php 7
9
I sent you a private message with the code
10
Can you explain me better please? Thank you
Pages: [1] 2 3 ... 10