Difference write scsi in Windows and Linux?

Hello. I will adapt the program under linux (Ubuntu) that has already been written on windows. This app works with the device developed by my colleague. The device (FAT32) connected to a PC, and is defined as a USB flash drive, a scsi Protocol. Later in my program the file is written to that device, and then there is the trouble: in Windows, the file is written, and in Linux not. Tried to record using the standard file-Manager - problem remained. What could be the problem and what the differences are in the recording file in Windows and Linux.
PS. I assume that the problem is scsi
P. p.s. the colleague who developed the device, is not up to me)
September 19th 19 at 00:01
1 answer
September 19th 19 at 00:03
If the record is on the level of operating system calls, the type and the interface media do not play a role.
Rather, the problem you have a level of access rights or the correctness of the transmission path(for example, handling of backslash).
Listened to the sniffer until it writes to the device in linux and windows. Alas could not naguglit intelligent manual with the commands to map the resulting set of bytes here and there, but I saw a pattern: 1) in Windows after you start recording, you first define the device, then the path, then the data record. 2) in Linux, on the contrary, as determined by the device, then the data record, and then the path where this data record. - Mackenzie43 commented on September 19th 19 at 00:06
The application program, usually at a low level writes, and uses system calls of the OS.
The record format of the file path in Windows and Linux are different. - Marianne_Bernier90 commented on September 19th 19 at 00:09

Find more questions by tags SCSIUSBLinux