Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 25

Thread: Installing FSX on Win10 ERROR 1310, 1304..

  1. Unhappy Installing FSX on Win10 ERROR 1310, 1304..

    I have been trying to install FSX standard (From installation CD) on my new, formatted, SSD drive (D:\FSX). This drive is NOT my boot/Win 10 drive.

    However, I keep getting these two error messages when it starts to install the files in the new Scenery folder:

    Error 1310. Error writing to file.
    D:\Scenery\NAMC\Texture\Alpha_lm.dds Verify that you have access to that directory.

    Error 1304. Error writing to file.
    D:\Scenery\NAMC\Texture\amb_bridge,dds. Verify that you have access to that directory.


    Then the installation stops and closes the window.

    What am I doing wrong? The drive is formatted (NTFS) and I am able to create a FSX folder on it with no problems.

    Scott
    Windows 10 Home 64bit. FSX Deluxe with Acceleration. Motherboard: ASUS Prime H310M-E R2.0 LGA1151 (Intel 8th Gen) DDR4 HDMI VGA H310 Micro ATX. Processor: Intel® Core™ i3-8350K. Video: EVGA GeForce GT 1030 DDR4, 02G-P4-6232-KR, 2GB SDDR4. Memory: Kingston (2X 8Gb) 16GB DDR4 2400Mhz.

  2. #2
    Join Date
    Mar 2005
    Location
    Memphis, TN.
    Posts
    1,650
    Blog Entries
    2

    Default

    your sig says W7 and you then say W10 install (but who am I to talk, I have both)

    not real sure of myself here but...
    are you starting the install via "autorun" when you insert the disk? Block autorun (insert disk while holding shift) and manually run installer "as Administrator": Right-click installer and select "run as administrator". You probably should run FSX.exe when it is installed also "as Administrator".

    If you still have permissions issues you may have to assign some permissions yourself manually (beyond my paygrade to describe how). I installed disk FSX on Win7 and FSX-Steam on my Win10 with no permissions issues so I doubt that this is normal. I had FSX disk on a non-os drive on my previous build, also with no permissions issues.

    best wishes for quick 'recovery' from unnecessarily stupid stuff...
    Loyd
    Last edited by llivaudais; 04-06-2020 at 01:03 AM.
    Hooked since FS4... now flying:
    self-built i7-4790 at 4 GHz; GA-Z97X mobo; GTX 970; 16GB gskill;
    quiet, fast and cool running.
    Win 7/64: 840 EVO OS; 840 EVO (500G) game drive;
    Win10/64: 850 EVO (500G) for OS and games
    A few Flightsim videos on YouTube at CanyonCorners

  3. #3

    Default

    Google it theres loads of suggestions out there - looks to be more of a windows issue than FSX

  4. #4

    Default

    Hi Vomaka,

    Looks like it might be a permissions problem, I found a similar problem regarding
    trying to install other programmes

    "Error 1310.Error writing to file: Verify that you have access to that directory."

    "The cause for this error is the fact that the required files or location is already in use
    by some other software. This means that Windows finds that the user is trying to
    overwrite a software that is already installed. It could also occur if the program
    installer does not have access to write to that directory."


    If you previously had FSX installed on your boot drive, there may be some registry
    entries leftover, and this is known to cause issues when trying to re-install FSX.

    The following link may be of use if that is the case,

    http://c-aviation.net/clean-reinstall-of-fsx/

    Good luck and stay safe.

    Richard




    Intel Core i7-4770K CPU Overclocked @ 4.60 GHz (Hyperthreading off)
    Cooler Master Liquid Cooling System 120 AIO
    16 GB G-Skill DDR3 PC3-12800 (800 MHz)
    Nvidia GeForce GTX1050Ti 4 GB Graphics Card GDDR5
    3x 500GB Western Digital Blue 3D SSD SATA III
    Creative Sound Blaster Z Ultra High-Performance Sound Card 5.1Ch 24Bit
    Avermedia HD-C985 Live video capture card
    Deepcool Tesseract Mid Tower PC Case
    NZXT Grid+ V2 Fan Controller + 3 case fans
    Windows10 64 Professional
    FS9 - FSX -FSX-SE
    CH Yoke and Rudder Pedals
    Track Hat
    "If the wings are travelling faster than the fuselage, it's probably a helicopter - and therefore unsafe !"

  5. Default

    First let me change/fix the error message that I hastily wrote in my first post..

    Error 1310. Error writing to file.
    D:\FSX\Scenery\NAMC\Texture\Alpha_lm.dds Verify that you have access to that directory.

    Error 1304. Error writing to file.
    D:\FSX\Scenery\NAMC\Texture\amb_bridge,dds. Verify that you have access to that directory.


    And yes, I did research the error message and tried the suggested fixes. None worked.

    I changed all the file, FSX folder and "D:" drive permissions to accept all users. (Read, Write, Etc..)

    The FSX installer still gives the error above when it tries to install those two files. All of the folders (Scenery, Texture, Etc..) have been created at this time. It fails when the file are copied to the Texture folder. At this stage there is no FSX "program" to remove/uninstall, the uninstaller has not been created. I then removed the FSX folder, and tried installing again. Same result.

    Out of frustration, I also tried to install FSX "Deluxe" and got the same errors with the same files above. I then removed the FSX folder, and tried installing again. Same result.

    As a last resort, I may try to install it in the default location to see if I get the same problem. Or, perhaps, install it in C:\FSX.

    The only thing that I may have done wrong is the way I formatted the drive(?) After I installed the SSD, I formatted it (NTFS) and assigned the drive letter (D:\). and the name "Flight Simulator". There were no problems or error messages, so I thought it worked. Funny, it only took about three seconds to format the drive (1tb).

    This is where I'm at...

    Scott
    Windows 10 Home 64bit. FSX Deluxe with Acceleration. Motherboard: ASUS Prime H310M-E R2.0 LGA1151 (Intel 8th Gen) DDR4 HDMI VGA H310 Micro ATX. Processor: Intel® Core™ i3-8350K. Video: EVGA GeForce GT 1030 DDR4, 02G-P4-6232-KR, 2GB SDDR4. Memory: Kingston (2X 8Gb) 16GB DDR4 2400Mhz.

  6. #6

    Default

    Have you searched your pc to see if you have any duplicates of these textures? Have you tried 'safe mode' as an option to install FSX (not even sure its possible tho?)
    I also run deluxe boxed version on win10 64bit - but not acceleration, could it be an issue with that?

  7. #7
    Join Date
    Apr 2013
    Location
    5 NM NE of EDXF
    Posts
    2,218

    Default

    Pomak249,

    No, it cannot be that. To install Acceleration, you first have to install DeLuxe, then Acceleration on top of that.

    For the correct installation of Acceleration, there are plenty of threads in this forum where the correct procedure is described.

    Jorgen

  8. #8

    Default

    clutching at straws this ones a complete mystery

  9. Default

    Hey, I just remembered something that might be the problem...

    When I was doing the install, I remember windows gave me a message with a red "X" on it that said something about rebooting the system to run a disk check to fix errors on the "D" drive. I just clicked past it and went on with the installation. "I'll deal with it later" I said. I was to busy trying to do the install to worry about it.

    Well, now is the time to worry about it. I'm thinking the SSD drive has errors and those sector errors are preventing FSX from installing the files.

    Let me do a chkdsk on the drive and let you know what I find. Probably a bunch of sector errors.. (On a SSD?)

    To be continued..

    Scott
    Windows 10 Home 64bit. FSX Deluxe with Acceleration. Motherboard: ASUS Prime H310M-E R2.0 LGA1151 (Intel 8th Gen) DDR4 HDMI VGA H310 Micro ATX. Processor: Intel® Core™ i3-8350K. Video: EVGA GeForce GT 1030 DDR4, 02G-P4-6232-KR, 2GB SDDR4. Memory: Kingston (2X 8Gb) 16GB DDR4 2400Mhz.

  10. Default

    Well, Here are the details of the recent Windows CHKDSK. It is unable to repair the problems...
    The files that it found are the (768) files that I copied off the two FSX CD's.
    ___________________________________________________________________________

    Log Name: Application
    Source: Chkdsk
    Date: 4/7/2020 3:22:39 PM
    Event ID: 26214
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-O30455L
    Description:
    Chkdsk was executed in read/write mode.

    Checking file system on D:
    Volume label is FLIGHT SIMULATOR.

    Stage 1: Examining basic file system structure ...
    768 file records processed.

    File verification completed.
    0 large file records processed.

    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    5 reparse records processed.

    854 index entries processed.

    Index verification completed.


    5 reparse records processed.


    Stage 3: Examining security descriptors ...
    Inserting an index entry with Id 108 into index $SII of file 9.
    Inserting an index entry with Id 113 into index $SII of file 9.
    Inserting an index entry with Id 114 into index $SII of file 9.
    Inserting an index entry with Id 115 into index $SII of file 9.
    Inserting an index entry with Id 116 into index $SII of file 9.
    Inserting an index entry with Id 117 into index $SII of file 9.
    Inserting an index entry with Id 118 into index $SII of file 9.
    Inserting an index entry with Id 119 into index $SII of file 9.
    Inserting an index entry with Id 11A into index $SII of file 9.
    Inserting an index entry with Id 11B into index $SII of file 9.
    Inserting an index entry with Id 11C into index $SII of file 9.
    Inserting an index entry with Id 11F into index $SII of file 9.
    Inserting an index entry with Id 123 into index $SII of file 9.
    Inserting an index entry with Id 124 into index $SII of file 9.
    Inserting an index entry with Id 125 into index $SII of file 9.
    Inserting an index entry with Id 127 into index $SII of file 9.
    Inserting an index entry with Id 129 into index $SII of file 9.
    Inserting an index entry with Id 12A into index $SII of file 9.
    Inserting an index entry with Id 108 into index $SDH of file 9.
    Inserting an index entry with Id 113 into index $SDH of file 9.
    Inserting an index entry with Id 114 into index $SDH of file 9.
    Inserting an index entry with Id 115 into index $SDH of file 9.
    Inserting an index entry with Id 116 into index $SDH of file 9.
    Inserting an index entry with Id 117 into index $SDH of file 9.
    Inserting an index entry with Id 118 into index $SDH of file 9.
    Inserting an index entry with Id 119 into index $SDH of file 9.
    Inserting an index entry with Id 11A into index $SDH of file 9.
    Inserting an index entry with Id 11B into index $SDH of file 9.
    Inserting an index entry with Id 11C into index $SDH of file 9.
    Inserting an index entry with Id 11F into index $SDH of file 9.
    Inserting an index entry with Id 123 into index $SDH of file 9.
    Inserting an index entry with Id 124 into index $SDH of file 9.
    Inserting an index entry with Id 125 into index $SDH of file 9.
    Inserting an index entry with Id 127 into index $SDH of file 9.
    Inserting an index entry with Id 129 into index $SDH of file 9.
    Inserting an index entry with Id 12A into index $SDH of file 9.
    Repairing the security file record segment.
    Write failure with status 0xc0000185 at offset 0xd00000 for 0x20000 bytes.
    Readable file record segment 9 is not writeable.


    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Chkdsk" />
    <EventID Qualifiers="0">26214</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-04-07T19:22:39.642980800Z" />
    <EventRecordID>4967</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-O30455L</Computer>
    <Security />
    </System>
    <EventData>
    <Data>

    Checking file system on D:
    Volume label is FLIGHT SIMULATOR.

    Stage 1: Examining basic file system structure ...
    768 file records processed.

    File verification completed.
    0 large file records processed.

    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    5 reparse records processed.

    854 index entries processed.

    Index verification completed.


    5 reparse records processed.


    Stage 3: Examining security descriptors ...
    Inserting an index entry with Id 108 into index $SII of file 9.
    Inserting an index entry with Id 113 into index $SII of file 9.
    Inserting an index entry with Id 114 into index $SII of file 9.
    Inserting an index entry with Id 115 into index $SII of file 9.
    Inserting an index entry with Id 116 into index $SII of file 9.
    Inserting an index entry with Id 117 into index $SII of file 9.
    Inserting an index entry with Id 118 into index $SII of file 9.
    Inserting an index entry with Id 119 into index $SII of file 9.
    Inserting an index entry with Id 11A into index $SII of file 9.
    Inserting an index entry with Id 11B into index $SII of file 9.
    Inserting an index entry with Id 11C into index $SII of file 9.
    Inserting an index entry with Id 11F into index $SII of file 9.
    Inserting an index entry with Id 123 into index $SII of file 9.
    Inserting an index entry with Id 124 into index $SII of file 9.
    Inserting an index entry with Id 125 into index $SII of file 9.
    Inserting an index entry with Id 127 into index $SII of file 9.
    Inserting an index entry with Id 129 into index $SII of file 9.
    Inserting an index entry with Id 12A into index $SII of file 9.
    Inserting an index entry with Id 108 into index $SDH of file 9.
    Inserting an index entry with Id 113 into index $SDH of file 9.
    Inserting an index entry with Id 114 into index $SDH of file 9.
    Inserting an index entry with Id 115 into index $SDH of file 9.
    Inserting an index entry with Id 116 into index $SDH of file 9.
    Inserting an index entry with Id 117 into index $SDH of file 9.
    Inserting an index entry with Id 118 into index $SDH of file 9.
    Inserting an index entry with Id 119 into index $SDH of file 9.
    Inserting an index entry with Id 11A into index $SDH of file 9.
    Inserting an index entry with Id 11B into index $SDH of file 9.
    Inserting an index entry with Id 11C into index $SDH of file 9.
    Inserting an index entry with Id 11F into index $SDH of file 9.
    Inserting an index entry with Id 123 into index $SDH of file 9.
    Inserting an index entry with Id 124 into index $SDH of file 9.
    Inserting an index entry with Id 125 into index $SDH of file 9.
    Inserting an index entry with Id 127 into index $SDH of file 9.
    Inserting an index entry with Id 129 into index $SDH of file 9.
    Inserting an index entry with Id 12A into index $SDH of file 9.
    Repairing the security file record segment.
    Write failure with status 0xc0000185 at offset 0xd00000 for 0x20000 bytes.
    Readable file record segment 9 is not writeable.

    </Data>
    <Binary>00030000520100004E0100000000000005000000000000000000000000000000</Binary>
    </EventData>
    </Event>
    __________________________________________________________

    What would be my next step in this? It seems that Windows can't repair the drive?

    Scott
    Windows 10 Home 64bit. FSX Deluxe with Acceleration. Motherboard: ASUS Prime H310M-E R2.0 LGA1151 (Intel 8th Gen) DDR4 HDMI VGA H310 Micro ATX. Processor: Intel® Core™ i3-8350K. Video: EVGA GeForce GT 1030 DDR4, 02G-P4-6232-KR, 2GB SDDR4. Memory: Kingston (2X 8Gb) 16GB DDR4 2400Mhz.

Page 1 of 3 1 2 3 LastLast

Similar Threads

  1. Replies: 3
    Last Post: 01-30-2020, 12:40 AM
  2. FSX will not start on Win10
    By snoopy0249 in forum FSX
    Replies: 2
    Last Post: 02-01-2019, 12:05 PM
  3. Replies: 3
    Last Post: 07-16-2018, 01:13 PM
  4. Replies: 8
    Last Post: 04-16-2018, 12:54 PM
  5. FSX won't run on Win10 without DX10?
    By ndts86 in forum FSX
    Replies: 1
    Last Post: 07-24-2016, 10:15 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •