Solved

Second IDE drive won't allow long filenames?

Posted on 1997-09-06
2
143 Views
Last Modified: 2013-12-16
I just installed a 1GB HD and when I pull it up under windows explorer, I cannot create or copy to it files with long files names;  all filenames must conform to DOS filenameing convensions.  How do I get it to accept long file names?  Configuration and installation details follow:

Pentium-90MHz, 24MB RAM, Windows 95 Version 4.00.950
I installed drive on second IDE cable from motherboard,
BIOS recognized it okay and assigned it to D:
FDISKed it as a primary partician,
Formated it from the FORMAT menu item on its icon under MY COMPUTER.
SCANDISKed it fine.
0
Comment
Question by:theowl
2 Comments
 
LVL 7

Accepted Solution

by:
busuka earned 20 total points
ID: 1750400
First of all:
- How BIOS recognise it ? Normal/Large/LBA
 - If it Normal you can't get more 504MB, but looks like you have
   HD works OK. If in 'IDE auto-identification' you specified Large
   change it to LBA and FDISK/FORMAT it immediately after.
   In Device Manager (CtrlPanel-Right_mouse_Click-Properties) remove
   it and let Win95 recognise it again.

If this not helped, post little more info:
 - if you have this HD in 'Compatibility mode' ?
 - What IDE controllers you have in Device Manager ?
 - if this HD shows up at all in Device Manager ?

0
 

Author Comment

by:theowl
ID: 1750401
All is working now.  Thanks!  You got it!

I checked the BIOS configurations again.  It read AUTO-DETECT on all items so I assumed it would work fine.  I changed the translation to LARGE BLOCK since that was an option.  I FDISKed it again, one change here...last time I configured the whole drive as one large 1GB Primary DOS Partician, this time I created a 480MB Primary DOS partician D:, and a 475MB Extended DOS partician with all space in a logical DOS Partician E:(I was told this would cut the minimum cluster size down from 32K to 16K, hence less wasted disk space).  Rebooted.  I then formated both particians from the MS-DOS window.  The E: drive immediately accepted long file names while the D: driver did not.  I re-booted and now both drives accept long file names...Why does LBA allow long filenames versus just LARGE?
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
When you try to extract and to view the contents of a Microsoft Update Standalone Package (MSU) for Windows Vista, you cannot extract the files from the MSU. Here we are going to explain how to extract those hotfix details without using any third pa…
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

832 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question