First post, by Sasha
Motherboard: don't know what it is
Processor type and speed: AMD Turion(tm) 64 X2 mobile Technology TL-64 2.20 GHz
Amount and type of RAM: 1918 MB and I don't know what type is
Video board w/ RAM amount and type:
Hmm, I don't know what that is, so here's what is on the display page, please indicate what this question was looking for:
Chip Type: ATI Radeon X 1200 Series (0x791F)
DAC Type: Internal DAC (400MHz)
Adapter String: ATI Radeon X 1200
Bios Information: RS690
Total Available Graphics Memory: 831 MB
Dedicated Video Memory: 128 MB
System Video Memory: 0 MB
Shared System Memory: 703 MB
Sound board: Same thing as video:
Realtek High Definition Audio
Device Type: Sound, video and game controllers
Manufacturer: Realtek
LLocation: Location 3 (Internal High Definition Audio Bus)
Operating system: Windows Vista Professional 32-bit
Game name: err, it's not a game, it's a programme, scandisk for Windows 95
Description of problem: this is getting too disjoint, I think I'll just describe the whole thing and then please indicate if you need other information and how to obtain the information from Vista.
I used to use regular scandisk to scan all my drives in the past. However, with Vista, even though it is a 32-bit version, I get the following error:
wrote:config.nt. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.
Close
(p.s. I like how they phrased it to "choose" close)
When I run Scandisk via DosBOX, however, it sets up the graphics and everything:
Microsoft Scandisk
──────────────────────────────────────────────────────────────────
It initializes the mouse and stuff, but it never does get around to scanning the disk itself. On the older version (before 0.63), it gives "Write 0 to rom at f392e" over and over again. This writing takes up a whole lot of CPU (in csrss.exe), so I figured perhaps a new version without it would work. However, even when the cycles are set to Max and priority set to Realtime, it only uses up in the 20s of CPU, though I doubt this is the reason, and it still doesn't work. I left it on overnight, but to no avail. The following commands have been used before scandisk:
mount C D:\ (drive to scan)
mount D F:\ (drive with scandisk programme)
D:
cd WIN95 (directory with scandisk programme)
scandisk C:
Edit: the D:\ (mapped C drive) has a FAT16 filesystem.
Any suggestions?