Hi Karen,
> let me simplify this some.
> I just did this about three hours ago. I have done nothing to the drive
> where the file was, in an effort of being very very sure it can be
> recovered.
As mentioned, the 2002 version of FreeDOS undelete avoids to write
the drive FROM which you extrac
Hi again,
given that I have very little information about your problem and
situation, I just give you a very big pile of ideas - maybe there
is something useful in it, or maybe something to ponder further.
>> First of all, I did not make myslf clear. I was not running win98.
>> I was only run
let me simplify this some.
I just did this about three hours ago. I have done nothing to the drive
where the file was, in an effort of being very very sure it can be
recovered.
granted dos 7.1 does not have undilute. dos 6.22 did, and I still have
that on a different drive.
I am not running f
Hi Karen,
> I xcopied the contents of my c drive to my e, which is a problem for
> one major file.
> if I want to recover this file as it was before the xcopy process, is
> there anything I can do?
Depends. If you deleted a file, you can try to undelete
it. In MS DOS, undelete starts at a del
On Sat, 09 Nov 2013 18:22:40 -0500, Rugxulo wrote:
>
> The two main files seem to be (as mentioned) fdos0138.exe (.ZIP sfx of
> .IMA) and jis4pack.lzh (three .fnt files, the first of which is huge,
> presumably only useful with something on the .IMA, perhaps FONTNX.EXE
> ??).
Yes, and they are b
On 11/09/2013 06:30 PM, Eric Auer wrote:
> Hi John,
>
>> to clarify, I ran sys c: from a freedos floppy to write over the win98
>> OS with freedos. that is how this all started.
> Ah, so you do not need Win98-DOS any more? That is easy :-)
>
> Actually the question then becomes: Apart from the Free
Hi John,
> to clarify, I ran sys c: from a freedos floppy to write over the win98
> OS with freedos. that is how this all started.
Ah, so you do not need Win98-DOS any more? That is easy :-)
Actually the question then becomes: Apart from the FreeDOS
warning about geometry, which is mostly cosm
Hi folks,
Interesting problem with my run of xcopy.
apparently when I put in this removable drive, the letters get goofy.
previously when I checked for example, the removable drive became e
shifting what is normally my e drive to f. this time though it became
something else without my realizing.
Hi,
On Sat, Nov 9, 2013 at 12:25 PM, John R. Sowden
wrote:
>>
> Wow!
> As usual when I present problems on these mailing lists, the solutions
> are complex. Nothings easy!
Welcome to computers, where "easy" means hours of work.
> I also have a tendency to not explain
> completely. Usually I'm
Hi,
On Sat, Nov 9, 2013 at 1:43 PM, TJ Edmister wrote:
> On Sat, 09 Nov 2013 00:36:49 -0500, Rugxulo wrote:
>
>> On Fri, Nov 8, 2013 at 8:02 PM, Matej Horvat
>> wrote:
>>>
>>> PS: I just wrote all that and found this:
>>>
>>> http://nokonoko365.cocolog-nifty.com/blogfile/freedos/index.html
>>>
On Sat, 09 Nov 2013 00:36:49 -0500, Rugxulo wrote:
> Hi,
>
> On Fri, Nov 8, 2013 at 8:02 PM, Matej Horvat
> wrote:
>>
>> ... irrelevant comments by me deleted ...
>>
>> PS: I just wrote all that and found this:
>>
>> http://nokonoko365.cocolog-nifty.com/blogfile/freedos/index.html
>>
>> Is that
On 11/09/2013 10:35 AM, Eric Auer wrote:
> Hi John,
>
>> As usual when I present problems on these mailing lists, the solutions
>> are complex. Nothings easy! I also have a tendency to not explain
>> completely. Usually I'm pretty precise. I am not running any MS
>> Windows on this computer. I
Hi John,
> As usual when I present problems on these mailing lists, the solutions
> are complex. Nothings easy! I also have a tendency to not explain
> completely. Usually I'm pretty precise. I am not running any MS
> Windows on this computer. I am running the "DOS 7.10" from Win98 on
>
On 11/09/2013 09:34 AM, Rugxulo wrote:
> Hi,
>
> On Sat, Nov 9, 2013 at 4:06 AM, Eric Auer wrote:
> - InitDiskWARNING: using suspect partition Pri:1 FS 0b: with calculated
> values
> 81-194-63 instead of 75-254-63
>> BIOS and partitioning disagree about CHS geometry and
>> your
Hi,
On Sat, Nov 9, 2013 at 11:34 AM, Rugxulo wrote:
>
> On Sat, Nov 9, 2013 at 4:06 AM, Eric Auer wrote:
>>
>> Win98 FAT32 typically does, but the message suggests that
>> you installed DOS on the partition. You can of course use
>> a Win98 DOS 7.x boot disk and just "SYS C:" again if the
>> res
Hi,
On Sat, Nov 9, 2013 at 5:13 AM, Matej Horvat
wrote:
> On Sat, 09 Nov 2013 06:36:49 +0100, Rugxulo wrote:
>> On Fri, Nov 8, 2013 at 8:02 PM, Matej Horvat
>> wrote:
>>> PS: I just wrote all that and found this:
>>>
>>> http://nokonoko365.cocolog-nifty.com/blogfile/freedos/index.html
>>>
>>> I
Hi,
On Sat, Nov 9, 2013 at 4:06 AM, Eric Auer wrote:
>
- InitDiskWARNING: using suspect partition Pri:1 FS 0b: with calculated
values
81-194-63 instead of 75-254-63
>
> BIOS and partitioning disagree about CHS geometry and
> your partition type 0b is FAT32 CHS. You could swit
On Sat, 09 Nov 2013 06:36:49 +0100, Rugxulo wrote:
> On Fri, Nov 8, 2013 at 8:02 PM, Matej Horvat
> wrote:
>> PS: I just wrote all that and found this:
>>
>> http://nokonoko365.cocolog-nifty.com/blogfile/freedos/index.html
>>
>> Is that third party software for Japanese support or what?
>
> No, a
On Sat, 09 Nov 2013 04:02:58 +0100, Eric Auer wrote:
> If that just returns a charset-specific static table, maybe it
> would be some sort of charset rendering and keyboard / input
> method driver that actually implements this, not the kernel?
Sure, it could also be a TSR. I forgot how flexible D
Hi John,
>>> - InitDiskWARNING: using suspect partition Pri:1 FS 0b: with calculated
>>> values
>>> 81-194-63 instead of 75-254-63
BIOS and partitioning disagree about CHS geometry and
your partition type 0b is FAT32 CHS. You could switch
to FAT32 LBA where geometry is irrelevant. Note tha
20 matches
Mail list logo
