Custom Query (69 matches)

I have written myself this batch file to do a chkdsk run just in case a removable volume is corrupted:

@echo off del d:\chkdsk.log>NUL & for %%D in (c: g: h: i: j: k:) do (if not exist %%D\. (echo Checking drive %%D & chkdsk %%D /F>>d:\chkdsk.log)) pause

This batch file works fine if the volume is managed by JFS.IFS but "if not exist %%D\." always fails on a volume managed by FAT32.IFS even if that volume is not corrupted. That's because FAT32.IFS does not report the existence of the "." and ".." directories.

Using the lastest release (R357) the ECS22 boot process stopped apparently after completing the processing of CONFIG.SYS with a black screen.

I did the following experiments

ECS22: R913 booted OK ECS22: R316 booted OK ECS22 R357 black screen ECS22 debug nucleus booted OK apart from a trap1 (responded "g")

[I recall that at the end of the experiments for ticket 67 R349 also did not compelete the boot except in debug mode)

ECS22/OS4: R357 black screen ECS22 OS4 Debug: R357 booted OK

ARCAOS: R349 booted OK.

Difficult to know what trace or other information I can add in the circumstances.

If I test an intact FAT16 volume "X:" with chkdsk, I get reported a "no error". If I rerun chkdsk I always get this:

[d:\]chkdsk x: /F |more

The current hard disk drive is: X:
The type of file system for the disk is FAT32.
The FAT32 file system program has been started.
FAT32: Unicode translate table for CP 437 loaded.
FAT32 version 0.10.r352 compiled on May  8 2018
The volume label is VFDISK.
The Volume Serial Number is 255D-E414.
The type of file system for the disk is FAT12.

CHKDSK is checking fats :Ok.
CHKDSK is checking files and directories...
CHKDSK is searching for lost data.
CHKDSK has searched   0% of the disk.
SYS0562: The system detected lost data on disk X:.
CHKDSK has searched 100% of the disk.

1 lost clusters found in 1 chains.
These clusters and chains will be erased unless you convert
them to files.  Do you want to convert them to files(Y/N)? 1 lost clusters found
 in 1 chains
These clusters and chains will be erased unless you convert
them to files.  Do you want to convert them to files(Y/N)?

I have also experienced this very same error with FAT32 formatted partitions. This error is new, I don't know when it started to show.

1) No matter if I select "Y" or "N", there are no lost clusters and therefore there is nothing to convert to a file.

2) Look at the screwed up screen text output. Something is going badly wrong in properly flushing the text to the text screen.

The only way to make this error go away is to reboot the system.